Methods and systems for determining obstruction setbacks in a photovoltaic system

ABSTRACT

A computer-implemented method for determining boundary offsets in a photovoltaic (PV) system based on shadow simulations is implemented by a design automation computer system in communication with a memory. The method includes identifying a set of obstructions wherein the set of obstructions includes a set of obstruction elevations and a set of obstruction offsets, simulating a set of shadow effects using a first coarse shadow algorithm based on the set of obstructions, refining the set of shadow effects using a second fine shadow algorithm based on the set of obstructions and the set of shadow effects, and defining a plurality of boundary of boundary offsets based on the refined set of shadow effects.

FIELD

The field of the disclosure relates generally to the design ofphotovoltaic systems. More particularly, this disclosure relates tomethods and systems to determine obstruction setbacks in the design ofphotovoltaic systems.

BACKGROUND

Designing and optimizing photovoltaic (PV) systems may be a complex andtime-consuming process. Effective design incorporates a variety of dataincluding location specific data, system type data, PV module data,design data, and layout data. Collecting such data may be a complextask. Further, a variety of calculations and modeling tools must be usedto effectively design and optimize such systems. Systems and methods forsimplifying such design and automation may be desirable.

This Background section is intended to introduce the reader to variousaspects of art that may be related to various aspects of the presentdisclosure, which are described and/or claimed below. This discussion isbelieved to be helpful in providing the reader with backgroundinformation to facilitate a better understanding of the various aspectsof the present disclosure. Accordingly, it should be understood thatthese statements are to be read in this light, and not as admissions ofprior art.

BRIEF SUMMARY

In one aspect, a method for designing a photovoltaic (PV) system isprovided. The method is implemented by a design automation computersystem in communication with a memory. The method includes receiving aset of site data, wherein the site data includes a set of locationidentifiers. The method also includes receiving a system type selection,receiving a plurality of system component selections, and receiving aplurality of PV layout preferences. The method further includesdetermining, at the design automation computer system, a PV modulelayout by iteratively applying a first layout algorithm to the set ofsite data and the plurality of PV layout preferences, the PV modulelayout defining a placement of a plurality of PV modules of a PV system.The method additionally includes determining a structural layout, anelectrical design, and an electrical layout based on the PV modulelayout, determining a bill of materials based on the PV module layout,the structural layout, and the electrical layout, and defining a PVsystem model using the structural layout, the electrical design, theelectrical layout, the PV module layout, and the bill of materials.

In another aspect, a design automation computer system for designing aphotovoltaic (PV) system is provided. The design automation computersystem includes a processor and a memory coupled to the processor. Thedesign automation computer system is configured to receive a set of sitedata, wherein the site data includes a set of location identifiers,receive a system type selection, receive a plurality of system componentselections, receive a plurality of PV layout preferences, determine a PVmodule layout by iteratively applying a first layout algorithm to theset of site data and the plurality of PV layout preferences, the PVmodule layout defining a placement of a plurality of PV modules of a PVsystem, determine a structural layout, an electrical design, and anelectrical layout based on the PV module layout, determine a bill ofmaterials based on the PV module layout, the structural layout, and theelectrical layout, and define a PV system model using the structurallayout, the electrical design, the electrical layout, the PV modulelayout, and the bill of materials.

Another aspect of the present disclosure is a computer-readable storagemedia for designing a photovoltaic (PV) system, the computer-readablestorage media having non-transitory, computer-executable instructionsembodied thereon. When executed by a design automation computer systemcomprising a processor and a memory coupled to the processor, thecomputer-executable instructions cause the design automation computersystem to receive a set of site data, wherein the site data includes aset of location identifiers, receive a system type selection, receive aplurality of system component selections, receive a plurality of PVlayout preferences, determine a PV module layout by iteratively applyinga first layout algorithm to the set of site data and the plurality of PVlayout preferences, the PV module layout defining a placement of aplurality of PV modules of a PV system, determine a structural layout,an electrical design, and an electrical layout based on the PV modulelayout, determine a bill of materials based on the PV module layout, thestructural layout, and the electrical layout, and define a PV systemmodel using the structural layout, the electrical design, the electricallayout, the PV module layout, and the bill of materials.

A further aspect of the present disclosure is a computer-implementedmethod for constructing a photovoltaic (PV) system. The method isimplemented by a design automation computer system including a processorand a memory coupled to the processor. The method includes receiving aset of site data, wherein the site data includes a set of locationidentifiers, receiving a system type selection, receiving a plurality ofsystem component selections, receiving a plurality of PV layoutpreferences, determining, at the design automation computer system, a PVmodule layout by iteratively applying a first layout algorithm to theset of site data and the plurality of PV layout preferences, the PVmodule layout defining a placement of a plurality of PV modules of a PVsystem, determining a structural layout, an electrical design, and anelectrical layout based on the PV module layout, determining a bill ofmaterials based on the PV module layout, the structural layout, and theelectrical layout, creating a plurality of PV system options using thestructural layout, the electrical design, the electrical layout, the PVmodule layout, and the bill of materials, providing the plurality of PVsystem options to a user device, receiving a PV system selectioncorresponding to one of the plurality of PV system options, andconstructing the PV system based on the PV system selection.

An additional aspect of the present disclosure is a computer-implementedmethod for determining boundary offsets in a photovoltaic (PV) systembased on shadow simulations. The method is implemented by a designautomation computer system in communication with a memory. The methodincludes identifying a set of obstructions wherein the set ofobstructions includes a set of obstruction elevations and a set ofobstruction offsets, simulating a set of shadow effects using a firstcoarse shadow algorithm based on the set of obstructions, refining theset of shadow effects using a second fine shadow algorithm based on theset of obstructions and the set of shadow effects, and defining aplurality of boundary of boundary offsets based on the refined set ofshadow effects.

A further aspect of the present disclosure is a design automationcomputer system for determining boundary offsets in a photovoltaic (PV)system based on shadow simulations. The design automation computersystem includes a processor and a memory coupled to the processor. Thedesign automation computer system is configured to identify a set ofobstructions wherein the set of obstructions includes a set ofobstruction elevations and a set of obstruction offsets, simulate a setof shadow effects using a first coarse shadow algorithm based on the setof obstructions, refine the set of shadow effects using a second fineshadow algorithm based on the set of obstructions and the set of shadoweffects, and define a plurality of boundary of boundary offsets based onthe refined set of shadow effects.

Yet another aspect of the present disclosure is a computer-readablestorage media for determining boundary offsets in a photovoltaic (PV)system based on shadow simulations. The computer-readable storage mediahas non-transitory, computer-executable instructions embodied thereon.When executed by a design automation computer system comprising aprocessor and a memory coupled to the processor, the computer-executableinstructions cause the design automation computer system to identify aset of obstructions wherein the set of obstructions includes a set ofobstruction elevations and a set of obstruction offsets, simulate a setof shadow effects using a first coarse shadow algorithm based on the setof obstructions, refine the set of shadow effects using a second fineshadow algorithm based on the set of obstructions and the set of shadoweffects, and define a plurality of boundary of boundary offsets based onthe refined set of shadow effects.

A further aspect of the present disclosure is a computer-implementedmethod for determining a system layout of a photovoltaic (PV) system.The method is implemented by a design automation computer system incommunication with a memory. The method includes receiving a firstselection of a system table, receiving a layout mode designation,identifying a system orientation, identifying a system spacing,receiving a layout detail designation, and applying a layout algorithmbased on the first selection of a system table, the layout modedesignation, the layout mode designation, the system orientation, thesystem spacing and the layout detail designation.

A further aspect of the present disclosure is a design automationcomputer system for determining a system layout of a photovoltaic (PV)system. The design automation computer system includes a processor and amemory coupled to the processor. The design automation computer systemis configured to receive a first selection of a system table, receive alayout mode designation, identify a system orientation, identify asystem spacing, receive a layout detail designation, and apply a layoutalgorithm based on the first selection of a system table, the layoutmode designation, the layout mode designation, the system orientation,the system spacing and the layout detail designation.

Yet another aspect of the present disclosure is a computer-readablestorage media for determining a system layout of a photovoltaic (PV)system. The computer-readable storage media has non-transitory,computer-executable instructions embodied thereon. When executed by adesign automation computer system comprising a processor and a memorycoupled to the processor, the computer-executable instructions cause thedesign automation computer system to receive a first selection of asystem table, receive a layout mode designation, identify a systemorientation, identify a system spacing, receive a layout detaildesignation, and apply a layout algorithm based on the first selectionof a system table, the layout mode designation, the layout modedesignation, the system orientation, the system spacing and the layoutdetail designation.

Various refinements exist of the features noted in relation to theabove-mentioned aspects. Further features may also be incorporated inthe above-mentioned aspects as well. These refinements and additionalfeatures may exist individually or in any combination. For instance,various features discussed below in relation to any of the illustratedembodiments may be incorporated into any of the above-described aspects,alone or in any combination.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a perspective view of an example photovoltaic (PV) module;

FIG. 2 is a cross-sectional view of the PV module shown in FIG. 1 takenalong the line A-A;

FIG. 3 is a block diagram of an example computing device;

FIG. 4 is a block diagram of an example PV system;

FIG. 5 is a flow diagram of an example method of designing aphotovoltaic (PV) system implemented by the design automation computersystem of FIG. 3; and

FIGS. 6-19 are detailed flow diagrams illustrating steps performed bythe design automation computer system of FIG. 3 to design a PV system.

Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION

Computer systems, such as design automation computer systems, mayinclude a processor and a memory. However, any processor in a computerdevice referred to herein may also refer to one or more processorswherein the processor may be in one computing device or a plurality ofcomputing devices acting in parallel. Additionally, any memory in acomputer device referred to may also refer to one or more memories,wherein the memories may be in one computing device or a plurality ofcomputing devices acting in parallel.

As used herein, a processor may include any programmable systemincluding systems using micro-controllers, reduced instruction setcircuits (RISC), application specific integrated circuits (ASICs), logiccircuits, and any other circuit or processor capable of executing thefunctions described herein. The above examples are example only, and arethus not intended to limit in any way the definition and/or meaning ofthe term “processor.” The term “database” may refer to either a body ofdata, a relational database management system (RDBMS), or to both. Adatabase may include any collection of data including hierarchicaldatabases, relational databases, flat file databases, object-relationaldatabases, object oriented databases, and any other structuredcollection of records or data that is stored in a computer system. Theabove are only examples, and thus are not intended to limit in any waythe definition and/or meaning of the term database. Examples of RDBMS'sinclude, but are not limited to including, Oracle® Database, MySQL, IBM®DB2, Microsoft® SQL Server, Sybase®, and PostgreSQL. However, anydatabase may be used that enables the systems and methods describedherein. (Oracle is a registered trademark of Oracle Corporation, RedwoodShores, Calif.; IBM is a registered trademark of International BusinessMachines Corporation, Armonk, N.Y.; Microsoft is a registered trademarkof Microsoft Corporation, Redmond, Wash.; and Sybase is a registeredtrademark of Sybase, Dublin, Calif.)

In one embodiment, a computer program is provided, and the program isembodied on a computer readable medium. In an example embodiment, thesystem is executed on a single computer system, without requiring aconnection to a server computer. In a further embodiment, the system isrun in a Windows® environment (Windows is a registered trademark ofMicrosoft Corporation, Redmond, Wash.). In yet another embodiment, thesystem is run on a mainframe environment and a UNIX® server environment(UNIX is a registered trademark of X/Open Company Limited located inReading, Berkshire, United Kingdom). The application is flexible anddesigned to run in various different environments without compromisingany major functionality. In some embodiments, the system includesmultiple components distributed among a plurality of computing devices.One or more components may be in the form of computer-executableinstructions embodied in a computer-readable medium.

As used herein, an element or step recited in the singular and proceededwith the word “a” or “an” should be understood as not excluding pluralelements or steps, unless such exclusion is explicitly recited.Furthermore, references to “example embodiment” or “one embodiment” ofthe present disclosure are not intended to be interpreted as excludingthe existence of additional embodiments that also incorporate therecited features.

As used herein, the terms “software” and “firmware” are interchangeable,and include any computer program stored in memory for execution by aprocessor, including RAM memory, ROM memory, EPROM memory, EEPROMmemory, and non-volatile RAM (NVRAM) memory. The above memory types areexample only, and are thus not limiting as to the types of memory usablefor storage of a computer program.

As used herein, “geographic site” refers to the location in which adesigned PV system may be located. As discussed herein, the entirety ofthe geographic site may not be used because of, for example,obstructions, boundary offsets, shadow setbacks, and partitioning of thegeographic site into sub-sites.

The embodiments described generally relate to automated design ofphotovoltaic (“PV”) systems. More particularly, the embodimentsdescribed relate to methods and systems for facilitating automatedanalysis and simulations to design PV systems. The methods describedherein are implemented by a design automation computer system. Themethods described herein include (i) receiving a set of site data,wherein the site data includes a set of location identifiers, (ii)receiving a system type selection, (iii) receiving a plurality of systemcomponent selections, (iv) receiving a plurality of PV layoutpreferences, (v) determining, at the design automation computer system,a PV module layout by iteratively applying a first layout algorithm tothe set of site data and the plurality of PV layout preferences, the PVmodule layout defining a placement of a plurality of PV modules of a PVsystem, (vi) determining a structural layout, an electrical design, andan electrical layout based on the PV module layout, (vii) determining abill of materials based on the PV module layout, the structural layout,and the electrical layout, and (viii) designing the PV system using thestructural layout, the electrical design, the electrical layout, the PVmodule layout, and the bill of materials.

As used herein, the structural layout, the electrical design, theelectrical layout, the PV module layout, and the bill of materials mayall be referred to as creating a general system layout or a “PV systemmodel.” The PV system model substantially defines a representation ofthe designed PV system.

Designing photovoltaic (PV) systems is a complex process. A variety ofdisparate data sets must be brought together and analyzed. Further, avariety of distinct decisions must be made in PV system designincluding, for example, geographic site selection, system componentselection, and layout preference selection. Each decision may cascadeand affect the available options for other decisions. Ultimately,designers of PV systems additionally consider the logistical andeconomic prospects of designed systems. Due to such voluminous data andnumerous choices, effectively identifying preferable PV system designsis a significant challenge.

Accordingly, the design automation computer system described herein isconfigured to facilitate the design of PV systems. In the exampleembodiment, the design automation computer system is in communicationwith external systems as described below. Such external systems allowthe design automation computer system to access external databases andleverage programs and algorithms of such external systems. The designautomation computer system may communicate with such external systemsvia any networking method. Further, as described herein, the designautomation computer system may be in communication with other devicesincluding user devices. In an example embodiment, users designing PVsystems access the design automation computer system via such userdevices. The user devices access the design automation computer systemover a network and may function in a client-server relationship whereinthe user device is a client and the design automation computer system isa server. In further examples, users may directly access the designautomation computer system via any suitable interface. In additionalexamples, the design automation computer system may substantiallyrepresent a cloud-based resource available to a plurality of userdevices.

In the example embodiment, users access the design automation computersystem using a graphical user interface (“GUI”). Because PV systemdesign involves simulation of the conditions of the PV system (e.g.,illustrating solar activity and shadows), the GUI may be useful forillustrating such simulations.

More specifically, as described herein, the systems described mayoperate in conjunction with modeling software and three-dimensionalmodeling software. In one example, the design automation computer systemmay integrate with such modeling software. The design automationcomputer system may also export and import design files from and to suchmodeling software. Such design files may be imported or exported in anysuitable format including a CAD format.

In some examples, the design automation computer system is configured todefine three-dimensional attributes and positions of all site features(e.g., site boundaries, obstructions, rows, and aisles) includingheights of such features. Further, the design automation computer systemmay be able to simulate shadow effects for features of the site andaccordingly develop a “shadow profile” to define the usable area of thesite. Additionally, the design automation computer system may generatethe PV model layout in three-dimensions. Further, the design automationcomputer system may run additional shadow simulations upon completion oflayout to determine how height and tilt of PV modules in the layout areshaded at a given date and time (and a given sun position). Moreover,the design automation computer system is configured to allow a user toplace components in the model including electrical and structuralequipment. Accordingly, the shade effects of such equipment may beconsidered and evaluated. The design automation computer system is alsoconfigured to create plan set drawings (including layouts and detailedviews) from a variety of perspectives by rotating the perspective of theuser in the three-dimensional environment. Also, the design automationcomputer system may facilitate the creation of line-of-sight studies touse with planning or zoning committees. The design automation computersystem may also facilitate creating reflectivity studies to demonstratethe periods of time that the PV system will reflect light onto a regionor regions. The design automation computer system further may facilitatecreating three-dimensional rendered designs for customers to evaluatethe design and aesthetics of the PV system.

In some examples, the defined designs of PV systems described herein maybe represented in a specialized format known as a “netlist” format. Thenetlist format may be used to transmit information regarding thedesigned PV system or to quickly query the PV system regardingattributes and structure of the PV system. Such efficient transmissionand querying may be useful for system maintenance and alerts. Forexample, field technicians may utilize the netlist format to quicklyfind a piece of equipment described in the PV system design (and thenetlist representation thereof).

In the example embodiment, the netlist format includes two componentsections. First, the netlist format includes a definitional sectiondefining components included within a system and their respectiveproperties. Second, the netlist format includes a hierarchicalrepresentation of the components from the point of interconnection downto each individual module. In the example embodiment, such hierarchicalrepresentation is provided in the netlist as a parent/child hierarchywherein each component is a child of the next level of component aboveit. The top level parent is the PV system itself.

The design automation computer system may also utilize a command lineinterface (“CLI”) to allow any command to be presented in a textualformat (in addition to graphical commands that are usable by the GUI).In the design automation computer system, the CLI may also be used torun “batch” files that list multiple commands in succession.Accordingly, the commands of such batch files may be executed insuccession. A user may therefore build a file of commands (e.g., tablecreation commands and layout commands) and use the file to generatemultiple permutations of PV system designs, run simulations of energyproduction for each design, and identify the optimal design based on thepermutations.

At initial setup, the design automation computer system receives a firstset of site data. The set of site data represents a depiction of ageographic site considered as a location for the PV system. The set ofsite data may include drawings or renderings of the geographic site. Inone example, the set of site data includes satellite images and terraindata. In a second example, the set of site data includes computer-aideddesign (“CAD”) drawings indicating the features of the geographic site.In a third example, the set of site data may represent locationidentifiers including, for example, geographic coordinates such aslatitude and longitude coordinates. In such examples, the designautomation computer system may retrieve further data such as satelliteimages and terrain data by accessing an external system containinggeospatial data.

The design automation computer system may also receive additional sitefeatures that are not included in the set of site data. For example, thegeographic site may include a tree that is not visible or indicated inthe set of site data. As the tree may be an obstruction relevant to thedesign of the PV system, the user may identify the obstruction andprovide it to the design automation computer system.

The design automation computer system also receives a set of locationidentifiers. The set of location identifiers (e.g., latitude andlongitude coordinates) substantially identify the physical locationassociated with the set of site data. In at least some examples, the setof location identifiers are provided explicitly from a user device. Inother examples, the set of location identifiers is derived from the setof site data using any suitable method including, for example, imageanalysis and metadata analysis.

The design automation computer system also identifies a north angle forthe set of site data. As used herein, the north angle is the anglebetween true north and the y-axis in a three-dimensional coordinatesystem that is used by the design automation computer system to createthe site model. In some examples, the north angle may be automaticallydetermined based on the set of location identifiers. In other examples,the north angle may be provided explicitly from a user device.

The design automation computer system determines a set of locationdesign characteristics (“local design data”) based on the set of sitedata. The local design data may be retrieved from a local database, anexternal system, or a plurality of external systems. Local design datamay include, for example and without limitation, seismic load data, windload data, snow load data, solar data, wetland area identification data,floodplain area identification data, soil data, and elevation data. Someexamples of external systems that may be used to retrieve local designdata include engineering society databases, government databases, andacademic databases. In at least one example, the design automationcomputer system utilizes application program interfaces (“APIs”) toaccess local design data from such external resources. In a furtherexample, the design automation computer system aggregates local designdata from a plurality of sources and stores such aggregated local designdata at an associated local design database. Local design data may bebeneficial in the design of PV systems, as described herein, to identifylocal variables and risks associated with the location of the set ofsite data. For example, a first location may be associated with highwinds. When designing a parking canopy system in the first location,such high winds may shear PV modules from the canopy. Accordingly,structural components may be utilized to mitigate the risk of highwinds. In a second example, a second location may be associated withregular flooding. When designing a ground mount system in the secondlocation, structural components may be utilized to mitigate the risk offlooding.

The design automation computer system also receives a system typeselection. More specifically, a user accessing the design automationcomputer system selects a type of PV system. In the example embodiment,the system type selection may be ground mount, rooftop, and/or parkingcanopy. In other examples, other system types may be selected andconfigured in manners consistent with those described herein.

In at least some examples, the design automation computer system alsoreceives layout region identifications and designations. Morespecifically, a user may identify a portion of the geographic siteassociated with the set of site data for use with the designed PVsystem. In one example, the user may graphically identify a subsectionof the geographic site that may be used. In further examples, the usermay provide a name for the subsection. The user may design multiple PVsystems in the same geographic site. Therefore, identifiers may beuseful to distinguish each subsection associated with a distinct PVsystem.

The design automation computer system may also receive a set of boundaryoffsets associated with the set of site data. The set of boundaryoffsets identify areas which cannot be utilized in the layout of the PVsystem. Such boundary offsets may be chosen for logistical purposes(e.g., to allow maintenance crews to access the PV system easily) or anyother reason. In one example, a rooftop system is selected and theboundary offset allows a walking path around the PV system formaintenance access. The set of boundary offsets may be identifiedgraphically.

The design automation computer system additionally may receive a set ofobstruction definitions associated with the set of site data. The set ofobstruction definitions define any obstructions that are located at thegeographic site. Examples of obstruction definitions may includeobstruction locations, obstruction heights, and obstruction offsets.Obstruction locations and obstruction heights may be providedexplicitly. Alternately, obstruction locations and obstruction heightsmay be determined by processing the set of site data using, for example,image analysis. In at least some examples, the design automationcomputer system may identify obstructions and obstruction heightswithout user input. Obstruction offsets reflect offsets associated withthe obstruction. In at least some examples, obstruction offsets aredetermined because of maintenance requirements. In the exampleembodiment, obstruction offsets are provided by a user at a user device.Further, in the example embodiment, the design automation computersystem avoids placing PV modules within obstruction offsets as suchplacement is inefficient.

Using the set of obstruction definitions, the design automation computersystem determines a set of shadow setbacks. More specifically, thedesign automation computer system identifies the set of obstructionsbased on the set of obstruction definitions and projects shadow effectson the geographic site for a plurality of time periods. The designautomation computer system identifies simulation time periods andidentifies a projected sun location for each time period. Using theprojected sun location, the design automation computer system projectsthe shadow effects of the sun and the set of obstructions on thegeographic site. In at least some examples, the user provides the timeperiods (e.g., dates and times) for simulating such shadow effects. Infurther examples, multiple PV module heights may be simulated to showvarying shadow effects based on the height of the PV modules. In suchexamples, the user may provide potential PV module heights.

Shadow Algorithms

In the example embodiment, the design automation computer system usesshadow algorithms to render shadow effects. The shadow algorithms arecritical to determine solar PV generation as the yield of the PV systemis affected if shadow falls on a functional solar panel. In order toensure that the designer is able to maximize placement of solar moduleswith minimal shadow implications, several options are provided to theuser of the design automation computer system, described below.

In a first example, shadow effects may be determined based on solstice.During winter and summer solstice the sun is at the lowest and highestpoint, respectively. In such an example, the shadow effects at winterand summer solstices are simulated for each of the days.

In a second example, the design automation computer system allows usersto additionally specify additional days for simulating shadow effects.In some cases, users may simulate shadow effects during the spring andautumn equinox.

In other examples, the design automation computer system allows a userto simulate shadow effects for every day of the year. In some cases,such simulations may be performed using an automated scripting solution.

In a fourth example, the design automation computer system may simulateshadow effects for a particular time range within days. Typically, theeffective yield from the sun for PV systems is between 9:00 AM and 3:00PM. Before sunrise and after sunset, no solar generation occurs. Inother words, the output of the PV system is significantly dependent onthe time of day—further, in many examples obstructions may only createshadow effects at particular periods of the day. For example, if aparticular obstruction casts a shadow after 2:30 PM, the designautomation computer system may simulate shadow effects before thisperiod to calculate yields and after this period to simulate shadoweffects.

In a fifth example, the design automation computer system may make timezone adjustments for shadow effect simulations. As described above, inmany PV systems, effective solar generation is between 9:00 AM and 3:00PM. However, within a particular time zone, sun position may varysubstantially for a particular time. For example, if a site is in alongitude of 75 degrees west, the sun position at 9:00 AM may bedifferent from a site at 80 degrees west within the same time zone eventhough the clock time is the same. The design automation computer systemmay adjust for such intra-time zone variance by calculating theeffective clock time for a site at a specific longitude. Thus, theeffective clock time at the longitude of 75 degrees west will vary fromthe effective clock time of at 80 degrees west.

In a sixth example, the design automation computer system may simulateshadow effects based on table height settings. The vertical placement ofPV modules may affect the shadow effects. For example, if PV modules areplaced at a height of two feet above the ground, all obstructions havinga height below two feet do not cause shadow effects on the PV modules.Accordingly, the design automation computer system may factor in theheight of the tables to determine whether certain obstructions may beexcluded from causing shadow effects.

Further, the design automation computer system may simulate shadoweffects at various table heights to maximize effective placement of PVmodules. For example, by simulating table heights at a variety ofheights, the design automation computer system may determine thatincreasing the table height by a given amount (e.g., six inches) inchesincreases the effective placement area by ten percent and the overallyield by five percent. Accordingly, the design automation computersystem may determine the preferable height of PV modules.

In a seventh example, the design automation computer system allows auser to simulate shadow effects at specific intervals between a startand an end time. In an example embodiment, the default interval is onceevery hour. Alternately, the design automation computer system maysimulate shadow effects at a smaller interval (e.g., every 30 minutes).More frequent simulations may allow for a more accurate simulation,generally.

In the example embodiment, two shadow algorithms are used to rendershadow effects. In a first example, a coarse algorithm is used. Thecoarse algorithm identifies obstructions based on the set of obstructiondefinitions and projects the shadow caused by each obstruction based onthe projected sun position vector for each period in the simulated timeperiod. The coarse shadow algorithm uses the sun position to projectshadows caused by obstructions onto a ground face. For every intervalfrom start time to end time of specific days of the year (as defined bythe user) and during periods of the day (as defined by the user) atdefined intervals, the sun position is determined.

For a specific sun position, a line drawn from the sun direction to eachof the obstructions is used to determine shadow effects. The designautomation computer system uses visible corners of each obstructionabove the table height and determines the projection of each obstructiononto the ground based on the sun position.

The design automation computer system repeats the coarse algorithm forvisible corners of each obstruction for every time interval within thestart and end times for each of the days specified.

The design automation computer system further connects the pointsrendered on the ground with the base of the obstruction to determinemultiple shadow regions. The shadow regions will often overlap betweentime intervals. The design automation computer system uses a unionalgorithm to join overlapping regions into a single region. The designautomation computer system repeats the union algorithm until multiplecontiguous regions of shadow are obtained.

In some cases, obstructions may have a large number of corners. In suchexamples, it may be difficult to perform a corner projection of each ofthe corners due to significant computational times. In such cases, thedesign automation computer system may determine an effectiveapproximation to take the bounding box of such complex objects and usethe bounding box corners for shadow rendering.

In such shadow effect simulations, various independent areas may becalled regions. For example in a site with multiple buildings, eachbuilding rooftop may be treated as a region. Accordingly, the designautomation computer system may substantially determine shadow effects(and all other aspects of PV design) with at a regional level.

In some examples, multiple regions may be identified within a site. Insuch a multi-region scenario, when simulating shadow effects for oneregion, other regions and associated obstructions may also render shadoweffects onto the simulated region. Accordingly, shadow effects may besimulated across regions.

The design automation computer system may simulate shadow effects (i.e.,apply shadow algorithms) on flat regions and on sloping, curved, ornon-level regions including sloping roofs. In many examples,obstructions on sloping roofs such as vents or chimneys may cause shadoweffects. The design automation computer system may determine shadoweffects of such obstructions on such non-level surfaces.

Once the shadow effects and shadow areas are determined by the coarsealgorithm, an additional process may be run to determine valid shadowareas. Specifically, the design automation computer system identifiesshadow areas outside the selected region and removes such outside areas.Accordingly, only the shadow areas are rendered.

The design automation computer system renders the shadow areas in ashadow layer. The shadow layer grouping is used to allow a user to showor hide the layer based on a single input (e.g., a selection or a mouseclick).

The shadow areas are also visually rendered at a slightly higher heightthan the ground region for display purposes. In other words, the shadowareas are rendered so that shadow regions may be distinguished fromground regions. In an example embodiment, the shadow areas are renderedat a scale depiction of one-quarter inch height above the ground region.Further, the design automation computer system may designate shadowareas by applying a different color to shadow areas to differentiatethem from other site areas and geometry.

In the second example, a fine algorithm is applied to refine the outputof the coarse algorithm. The fine algorithm may provide a more accurateshadow area representation and may also determine the approximation ofcomplex objects as explained above. The fine algorithm performs sunposition ray tests at short distance increments (e.g., less than 6inches) in order to create higher resolution shadow effects. The finealgorithm therefore produces a more precise shadow effects through thisdetailed simulation.

In the fine algorithm, the design automation computer system utilizes adifferent approach for determining shadow effects as compared to thecoarse algorithm. Specifically, the design automation computer systemuses the shadow areas as determined in coarse algorithm and does areverse shadow analysis. Each shadow area is broken into smaller squaresand a beam of light is simulated from the center of the each squaretowards the direction of the sun at the same interval periods as used inthe coarse algorithm. Accordingly, between the start and end times (atthe specified interval for each of the days to be tested), the designautomation computer system simulates sending a ray towards the sunposition. The design automation computer system determines whether theray intersects with an obstruction. If the ray intersects with anobstruction, the smaller square is verified as a shadow square (i.e., asquare that is verified to have a shadow effect). This process may berepeated for all smaller squares for each shadow areas for specifieddays and times. The size of the smaller square may be determined by thesize of the site and the amount of time it takes to compute the shadow.In many examples, a very large site may use larger squares while smallersites may use smaller squares. In some examples, the maximum length ofthe side of each square is set to twelve inches to maintain accuracy. Insome examples, the minimum length of the side of each square is limitedone inch to maintain the efficiency of calculation.

In most embodiments, the coarse and fine algorithms are configured to beexecuted in a limited period of time on a user computing device such asa desktop or a laptop. However, in other examples, processingcapabilities and time may not be as crucial and the square size may bedecreased below one inch per side. Similarly, more frequent simulationsmay be used. In some examples, such simulations may be performed on aremote server accessible by a user computing device.

Once the shadow squares are determined, a union algorithm similar tothat described above may be executed to combine all shadow regions intocontiguous areas and all non-shadow regions into contiguous areas.Non-shadow contiguous areas may be deleted and the design automationcomputer system renders only shadow areas.

Similar to the coarse algorithm, the fine algorithm groups all shadowareas into a shadow layer for visibility, selection, and grouping.Further, also like the coarse algorithm, the fine algorithm may rendershadow effects for non-level surfaces. Additionally, also like thecoarse algorithm, shadow areas may be rendered at a default height ofone-quarter inch above the ground region in the fine algorithm.Additionally, the fine algorithm may distinguish shadow areas withdistinct colors in a manner similar to the coarse algorithm.

In some examples, the shadow algorithm may allow users to place allsolar panels in the entire usable area including possible shadow areas.In such examples, a process similar to the fine algorithm may be used todetermine shadow effects on the solar panels placed in potential shadowareas. Solar panels may be partitioned into smaller squares and asimulated ray may be sent towards the sun position for each of the daysbetween the start and end times for the specific days. The designautomation computer system may then determine a number of points inshadow and a number of points outside shadow and further determine aratio is of the points. The determined ratio may be used to determinethe gradient color of the solar module. In some examples, the solarmodule may be rendered in red if it is fully under shadow for all thedays and time intervals. Conversely, the solar module may be rendered ingreen if it is not in a shadow area at any point in the period. Thus,the solar module may be rendered in a varying color (on a gradient fromred to green) if the modules are partially shaded at particular points.

As a result, the design automation computer system may render the solarmodules to easily indicate highly shaded or fully shaded modules.Accordingly, a user may remove highly shaded or fully shaded solarmodules from the design. In some examples, a numeric value associatedwith the gradient value may also be displayed. Further, the designautomation computer system may provide a filter function to allow forremoval of all solar modules with gradient values outside the boundaryof the filter.

Shadow effects represent areas where PV systems will not yield optimalenergy production (because of the temporary or total reduction in solarirradiance at the location). Accordingly, it may be undesirable to placePV modules where obstructions cause shadow effects. The designautomation computer system therefore integrates the set of shadow effectareas into an integrated shadow setback area. The integrated shadowsetback area is used as negative space to define where the PV modulesshould not be placed.

The design automation computer system also receives a plurality ofsystem component selections. System component selections represent theselections of equipment that will be used by the PV system for energyproduction and transfer. Accordingly, in most examples, systemcomponents include PV modules, PV inverters, PV combiners, conductors,and conduits. In the example embodiment, the design automation computersystem identifies potential system component selections from a componentlibrary. As used herein, the “component library” refers to a data storethat catalogues components used in PV system design. The componentlibrary includes definitions and identifiers for system components,structural components, and electrical components. Further, the componentlibrary identifies which components may be used with other components.(In at least some examples, some system components may only be used witha subset of other available system components.) The component librarymay be stored in any suitable form.

In the example embodiment, the component library is stored in a databaseassociated with the design automation computer system. In at least someexamples, the component library also includes schematic information,safety information, pricing information, and maintenance informationassociated with components. In further examples, the component librarymay include estimated labor costs associated with components to identifythe cost of, for example, installation and maintenance.

The design automation computer system provides a retrieved plurality offirst system component options to a user device based on the componentlibrary. In other words, the design automation computer system presentssystem component options to the user based on the component library.Upon a component selection by the user, the design automation computersystem receives a first system component selection corresponding to oneof the plurality of first system component options from the user device.In the example embodiment, the first system component options representa set of PV module options. In other examples, other components mayfirst be presented to the user.

Upon receiving a first system component selection, the design automationcomputer system may constrain the available system component optionsbased on the first system component selection. As described above, atleast some components are associated with a subset of other componentsand therefore force a filtering of subsequent system component options.The design automation computer system accordingly retrieves a pluralityof second system component options associated with the first systemcomponent selection from the component library. In other words, thedesign automation computer system provides a second set of componentoptions from the component library based on the selection of the firstset of component options as the first selection acts as a filter on thecomponent library selections. For example, the first system componentoptions may include a list of conductor types including “aluminumconductors.” Upon selection of “aluminum conductors”, the designautomation computer system may provide a second set of component optionsfrom the component library representing all aluminum conductors noted inthe component library. The design automation computer system presentsthe plurality of second system component options to the user device andreceives a second system component selection corresponding to one of theplurality of second system component options from the user device. Inthe example embodiment, the second system component options represent aset of PV inverter options. In other examples, other components maysecondly be presented to the user.

In a similar fashion, the design automation computer system may presenta plurality of system component options to the user device until allsystem component options are identified for the purposes of PV systemdesign. In other examples, only a subset of system components isselected and the design automation computer system automaticallyidentifies suitable system components for the remainder of the PV systemdesign. In an example embodiment, a user selects a PV module, a PVinverter, and a PV combiner and the design automation computer systemautomatically selects a conductor and a conduit.

The design automation computer system also defines a PV module layout. APV module layout represents a physical layout of PV modules within thegeographic site. In at least some examples, PV module layouts follow ahierarchical convention wherein a group of PV modules may be identifiedas a single unit known as a “table”. A table typically has fixeddimensions in terms of PV modules. A table may further be grouped into a“block”. Similarly, a block typically has fixed dimensions in terms ofPV tables.

To define the PV module layout, the design automation computer systemmay receive a table identifier from the user device to distinguishtables. The design automation computer system further identifies a PVmodule type for the table, previously selected by the user.

The design automation computer system calculates a recommended “stringsize” for the PV system. A string size represents the amount of PVmodules that may be wired in succession. The string size may bedetermined based on electrical and temperature considerations. Thestring size may also be used by the design automation computer system todetermine the number of modules to be used in a table. As string sizesincrease, potential open-circuit voltage outputs for the stringsimilarly increase. The design automation computer system calculates therecommended string size by identifying and processing a plurality ofvariables. The design automation computer system identifies a proximateweather data source (e.g., an ASHRAE station) and receivesmeteorological data for the geographic site based from the proximateweather station. In the example embodiment, the received meteorologicaldata includes record high and record low temperatures for the geographicsite. The design automation computer system may be accessed using anassociated API or a data feed. The design automation computer systemalso receives electrical properties including, but not limited to,open-circuit voltage for the identified PV module and maximum powerpoint tracking ranges for the identified PV inverter. The values forsuch electrical properties may be retrieved from the component library.

Based on such electrical properties and meteorological data, the designautomation computer system determines a recommended string size for thePV system. In the example embodiment, the recommended string size is thequantity of PV modules in a string that results in an open-circuitvoltage that is within the maximum power point tracking range duringrecord low and record high temperatures for the geographic site.

The design automation computer system provides the recommended stringsize to the user via the user device. The user may select therecommended string size or choose an alternate string size. In at leastsome embodiments, users may only select string sizes that result inopen-circuit voltage that is within the maximum power point trackingrange during record low and record low temperatures for the geographicsite.

The design automation computer system also receives a selection of anamount of modules in the table. The selection may represent a selectionof strings per table or a selection of modules per table.

The user may further define customized layout properties for the table.In at least some examples, such customized layout properties include PVmodule orientation, row counts, tilt angles of the PV module, andspacing between rows and columns of the PV table.

The PV string size selection, the selection of an amount of modules inthe table, and the customized layout properties may be described as “PVlayout preferences.” Based on the PV layout preferences, the designautomation computer system may define each PV table.

As noted above, PV tables may be grouped into PV blocks. The designautomation computer system may receive a selection by the user toaggregate tables into blocks. Specifically, the design automationcomputer system may receive a selection of a defined PV table and aselection of the quantity and distribution of tables within the block.The design automation computer may further receive typical spacingbetween tables. Such spacing may be useful to facilitate maintenance ofeach table. Based on such user input, the design automation computersystem defines PV blocks.

Depending upon the selected system type, the design automation computersystem receives additional PV layout preferences. If the PV system is ofa ground mount or rooftop type, the design automation computer systemreceives an additional distinct set of PV layout preferences. The designautomation computer system receives a selection of one or more PV tablesor PV blocks being used in the design. The design automation computersystem also identifies whether the layout mode is “uniform” or“non-uniform”. When the layout mode is uniform, the design automationcomputer system may substantially automate the layout by repeating PVmodule dimensions and spacing. When the layout mode is non-uniform, thedesign automation computer system places PV modules as close as possibleto one another in order to maximize the energy output of the PV system.Accordingly, the uniform layout mode reflects a preference for arepeated spacing of PV modules while a non-uniform layout mode reflectsa preference for maximum energy output. The design automation computersystem also receives a layout alignment selection. The layout alignmentselection represents the selection of the axial orientation of the PVmodules by the user. Specifically, the design automation computer systemreceives an axial orientation from the user device. In the exampleembodiment, PV layout is along a north-south axis. In an alternativeembodiment, the user device may transmit any suitable axis oforientation. In some embodiments, the design automation computer systemmay receive a user input to define the azimuth. For example, a user mayselect a site feature (e.g., a boundary edge of a site) and the designautomation computer system may determine the azimuth based on theselected site feature and use the determined azimuth to define the axisof orientation. Based on the layout alignment selection, the designautomation computer system calculates an azimuth value. The designautomation computer system also determines a recommended spacing betweenrows of the PV tables. The recommended spacing may be determined byrunning a shade analysis algorithm to simulate shadow effects caused byeach row of PV modules. In the example embodiment, the shade analysisalgorithm is run over the winter and summer solstice periods between 10AM and 2 PM. The row spacing is therefore determined by identifying therow spacing that allows for shade-free rows of PV modules in thesimulated time periods. The design automation computer system receives auser selection for row and column spacing. The user may adopt therecommended spacing or select their own. The design automation computersystem may receive additional spacing preferences from the user device.Such additional spacing preferences may be provided by the user forreasons including logistics and access. The design automation computersystem receives the user selection for row and column spacing and theadditional spacing preferences as received user spacing selections. Insome examples, the user may additionally provide a maximum system size(or total system size) to indicate that the design automation computersystem should not layout a system exceeding this defined system size.The design automation computer system also receives a layout detailselection. Layout detail substantially represents the amount of timethat the design automation computer system may execute to identify PVlayout options. A higher value of layout detail may yield a higher PVsystem size. However, a higher value of layout detail may require moretime to process. Additionally, the design automation computer system mayreceive a layout region to identify the specific portion of thegeographic site that may be used for defining PV layout options.

Layout Algorithm

In the described example (wherein the PV system type is ground mount orrooftop), the design automation computer system uses the site data andthe plurality of PV layout preferences to determine the PV modulelayout. More specifically, the design automation computer systemiteratively applies a plurality of layout algorithms to determine the PVmodule layout. In an example embodiment, the design automation computersystem applies at least a first layout algorithm and a second layoutalgorithm. The first layout algorithm is applied to the set of site dataand the plurality of PV layout preferences. The first layout algorithmis used to maximize placement of solar modules in a site givenobstructions, shadow setbacks (and shadow effects) and boundary offsets.As described below, the second layout algorithm is used to iteratethrough the PV module layout and place structural components.

The first layout algorithm allows flexibility of user solar moduleplacement by providing layout options including those described below.As a result, the design automation computer system allows a user tocompare layouts based on the inputs provided.

In a first example, the design automation computer system provides auser options of tables or blocks to be used in the layout. As describedabove, tables are a collection of modules that are grouped together.Accordingly, tables allow for easy placement, particularly in largeregions. Tables allow the rapid placement of groups of modules in largespaces. Tables also may have structural components defined within.

As used herein, a “string” describes a set of modules serially connectedtogether. All direct current electrical connections in the PV world arebased on strings. Strings may be connected to inverters and combiners.

As used herein, “string size” refers to the number of modules in astring. String size may be determined based on at least module,inverter, and location characteristics. Accordingly, groups of moduleswithin a table may be determined based on string size. Morespecifically, modules may typically be grouped in multiples of a stringsize.

For smaller sites, to maximize solar module placement, tables may becreated with a fraction of a string size because having tables with theentire string size (or multiples thereof) may result in wasted space.Tables may also be created with solar modules in the table in portraitor landscape mode (i.e., with varying aspects). Tables may also becreated with multiple rows.

In the design automation computer system, tables may also be createdwith distinct types. In a first example, tables may be of a fixed tilttable type. In this example, modules may be placed in the east-westdirection while facing south in the northern hemisphere and north insouthern hemisphere. Each module may also be tilted at an angle. Thetilt of each module may be calculated based on the latitude andlongitude and direction of the sun in order to determine maximum solarenergy yield. The tilt of each module may be fixed in some examples andvariable in others. Accordingly, a user may select a fixed tilt tableand identify an orientation and angle for modules in the table.Alternately, the orientation and/or angle may be determined by thedesign automation computer system automatically.

In a second example, tables may be of a tracker table type. In suchexamples, modules may be placed in a north-south direction and followthe sun during the day. As the sun rises in the east and sets in thewest, tracker tables may be tilted by motors to follow the sun.Accordingly, tracker tables may have higher yields because the sunincidence on the module is typically perpendicular resulting in higheryields. Accordingly, the design automation computer system allows a userto designate a table as a tracker table.

In a third example, tables may be of a canopy table type. Canopy tablesrefer to table structures that may be placed on top of parking lotcanopies. There are three sub-types of canopy tables: gable, Y-type andsingle tilt. As described, each sub-type may be associated with avarying parking canopy layout because parking canopies may be laid outin a variety of ways. Typically parking canopies have two horizontalspans at various angles. In some examples, one span may be horizontaland one span may be tilted. Alternately, both spans may be in aV-configuration. In additional examples, the spans may be in an invertedV-configuration. When the tilts are in a V-configuration, Y-type canopytables may be appropriate. When the spans are in an inverted Vconfiguration, gable type canopy tables may be appropriate. Both thegable and Y-type canopy tables are capable of supporting differentangles for both spans. In a third example, the single tilt table typemay be used when both spans may be treated as a single span with asingle tilt.

As used herein, “blocks” may define another grouping of modules that isorganizationally at a higher level grouping than tables. Blocks aretypically composed of tables. In most examples, blocks are used on largeground mount sites. Blocks may be used to create a standardized set ofcomponents that are repeatable on large sites. Blocks typically includetables and associated components including inverters, combiners, andoptional structures. In most examples, a large site may use identicalblocks or similar blocks and place such blocks adjacent to one another.As described, blocks consist of tables placed in rows and columns withfixed spacing between the rows and columns. A user may define blocks byselecting a table to be used (as the underlying component), the blockdimensions (i.e., the number of columns and number of rows of tableswhich constitute a block) and the spacing between the tables of theblock.

The design automation computer system may also provide the option ofselecting multiple tables for a layout. Multiple tables may be chosenbased on certain criteria. For fixed tilt tables, multiple tables withthe same dimensions in the north direction may be selected. Typically,fixed tilt tables with one quarter of a string size, one half a stringsize, and a full string size may be selected for layout. The firstlayout algorithm may use all the three tables to create a layout withmaximum space used for layout.

For tracker tables, multiple tables with same dimension in the east-westdirection may be selected for layout. For example, a single stringtable, two-string table and three-string table may be selected.

After selecting the tables (or multiple tables), the user may select alayout mode. The design automation computer system includes are twolayout modes: a uniform layout mode and a non-uniform layout mode.

Uniform layout ensures rows of tables are placed in symmetrical fashion.If a user chooses multiple tables, the table with the largest dimensionis used and placed sequentially in each row. If, in a particular row thesecond table cannot be placed due to an obstruction, that space istotally ignored and the table is placed in the third column as theprevious rows. If the unused space can accommodate smaller tableswithout encroaching on the third column, the smaller tables are placed.If not, the space is ignored and tables are placed in equal intervals oflargest table size. This mode of layout results in clean, well definedtable layouts with clean pathways.

Non-uniform layout may be used in sites where the number of obstructionsis high. In the non-uniform layout mode, tables are placed in asequential fashion. If a larger dimension table cannot be placed asmaller table is placed. However, rather than move to the next column toplace the next table like in uniform mode, the largest table is placedimmediately next to the smaller table. Thus, the non-uniform layout moderesults in densely packed tables but while lacking the symmetry ofuniform layout mode. Non-uniform layout mode may be used if maximumyield is of paramount importance or if sites are highly obstructed.

The design automation computer system may receive a user specifiedazimuth angle value. Azimuth angle defines how the tables face the sun.For example, in the northern hemisphere, the azimuth value is 180° whilein southern hemisphere the azimuth angle is 0°.

The design automation computer system allows a user to select one of thetwo options. The user may align to true south or align to off-azimuth.When aligning to true south is selected, the azimuth angle is 180° asexplained above. When aligned to off-azimuth is selected, a user mayspecify an off-azimuth angle. Off-azimuth angle may be used in exampleswhere a site is slightly slanted and is not facing south. Placing tablesfacing south on such a site may result in fewer numbers of placed tablesdue to the slant of the site. Therefore, by adjusting for the slightoff-azimuth angle, the design automation computer system may align thetables to the site boundaries to obtain maximum table placement.

The design automation computer system may also allow a user to specifythe north-south gap for layout. This is gap in the north-southdirections between rows of tables. The north-south gap may be specifiedas a pitch value. “Pitch”, as used herein, is defined as the distancebetween two successive tables in the north direction.

The north-south gap may also be specified as a ground coverage ratio(“GCR”). GCR, as used herein, is a ratio of the length of the table innorth-south direction in comparison to the pitch. Thus, a GCR of 100%indicates that tables are placed in rows without any gap. Alternately, aGCR of 50% means the gap between tables in the north-south direction isequal to the length of the table. Therefore, in this case half the siteis covered by tables.

Additionally, the design automation computer system allows foradditional types of gaps. In some examples, a user may want to defineroadways or pathways for vehicle movement within the site. The designautomation computer system allows for the definition of such pathwaysusing additional north-south gaps. The design automation computer systemallows a user to choose such additional north-south gaps by specifying agap for every specific number of tables in the north-south direction.For example, a ten foot gap every five tables would create a ten footpathway running east to west after every five tables in the north-southdirection.

The design automation computer system also allows a user to chooseadditional north-south gaps by specifying a gap after a specificdistance. For example, if a ten foot gap every two hundred feet isspecified, a ten foot gap is created every two hundred feet. However, iftables are placed such that a table exists at the two hundred footpoint, the additional gap may be created after the placement of thetable nearest the two hundred foot point.

The design automation computer system also allows a user to specify theeast-west gap for layout. The east-west gap is a gap in the east-westdirection between columns of tables. The east-west gaps may be definedand used in a similar manner as the north-south gaps.

The design automation computer system also allows a user to specify themaximum system size allowable for placement. In some examples, due tocustomer or regulatory constraints, it may be required that a particularsite should not exceed a specific system size. Accordingly, a user mayspecify the maximum system size in at least two ways. In a firstexample, an “at least” mode will place tables whose total kilowattdirect current meets at least a specified value. For example, each tablemay be three kilowatts in size. If user specifies 250 kilowatts “atleast”, the design automation computer system will determine a layoutincluding eighty four tables totaling 252 kilowatts.

In a second example, an “at most” mode will place tables whose totalkilowatt direct current is at most the specified value. For example,each table is three kilowatts in size. If user specifies 250 kilowatts“at most”, the design automation computer system will determine a layoutincluding eighty four tables totaling 249 kilowatts.

The design automation computer system also allows a user to specify astart point. A start point denotes the starting place where tables areplaced and the direction and orientation of table placement. Start pointmay be specified in multiple ways. A start point may be identified at anorigin causing the design automation computer system to place tablesstarting at the lower left corner of the site.

User may also optionally specify the direction of table placement. Bydefault, the design automation computer system places tables in aneast-west direction and, upon completion of a row, moves to the next rowand repeats the process.

In a second example, the user may designate a start point at the centerof the site and the design automation computer system may start tableplacement at the center of site. While starting at the center, the usermay specify that tables should be placed in the lower half of the siteonly. The user may then specify that table placement happens ineast-west direction first for each row and moves only in the southdirection afterwards.

In a third example, the user may choose a custom point on site as thestart point. This is typically used to concentrate tables in one area ofthe site because a user has specified a maximum system size which issignificantly smaller than what the site can accommodate. For example,if user has a large site which may accommodate one thousand kilowatts,but regulatory requirements require three hundred kilowatts only on thissite, a user may potentially choose a region closest to a roadway toplace modules in an accessible location.

The design automation computer system also allows the user to choose thetype of “layout run”. Layout run determines a level of detail fordetermining layouts. More specifically, layout runs designate the numberof different start points to iterate through closest to the start pointspecified earlier. In the example embodiment, three types of layout runsare available: Quick Run, Normal Run, and Detailed Run. As indicated bythe names, Quick Run includes the fewest numbers of start points, NormalRun includes an intermediate number of start points (including all ofQuick Run start points), and Detailed Run includes the most start points(including all of Normal Run and Quick Run start points).

After the user chooses all the described inputs, the first layoutalgorithm uses the above inputs to layout tables. As described herein,various independent areas are called regions. For example in a site withmultiple buildings, each building rooftop is treated as a region.Accordingly, the first layout algorithm may operate in a region-basedmanner.

The design automation computer system allows the user to choose a regionto perform a layout. The first layout algorithm determines the directionof layout based on start point and directions specified. Additionally,the first layout algorithm determines the order of placement. Typically,it places tables in an east-west direction and then moves in the northdirection and continues the process until the full site is completed orthe maximum system size is achieved.

For certain types of tracker installations, the direction of tableplacement is in the north-south direction and then moves to the east andplaces the next set of tables in north-south direction.

The design automation computer system determines a direction ofplacement based upon a user selection for start point selection asexplained above. For each start point, as determined by the layout run,tables are placed on the site sequentially in the requested direction.If a table can be placed without any obstruction or a shadow keep outintersecting it, the table is placed. The design automation computersystem repeats such a process for each row and then it moves to thestart of the next row. The design automation computer system determinesthe start of the next row based upon the pre-defined north-south gap.Accordingly, the design automation computer system places the tables inthe second row.

The design automation computer system repeats such placement until theentire site is covered or the maximum system size is reached. In anexample embodiment, the total number of tables, the corresponding inputparameters associated with a layout, and table positions may be storedas a data structure on any storage suitable for later retrieval. Such adata structure may be referred to as a layout result set. The designautomation computer system chooses the second start point closest to theuser selected start point and performs the same set of table placementsas described above. Similarly, the results of this second iteration maybe stored on any suitable storage. Accordingly, the design automationcomputer system performs the above-described steps for each start pointbased upon the selected layout run type (e.g., Quick Run, Normal Run,and Detailed Run).

In each example, results of each iteration may be stored. During thelayout process, the design automation computer system may allow a userto cancel or abort the layout process. In an example embodiment,canceling or aborting stops the first layout algorithm from proceedingand renders the last rendered (and completed) layout on the visualdisplay.

If a user does not abort or cancel the layout run, the design automationcomputer system retrieves all stored layout results and determines alayout resulting in the highest KW for the site and renders that layouton the visual display.

The design automation computer system allows the user to continueperforming a layout for all the regions on the site. The user may alsoundo the layout for a particular region which may clear the tables inthe region. The user may also layout tables on a region alreadycontaining tables. Accordingly, the design automation computer systemprompts the user to clear the tables previously placed and place thetables in the region based on the new set of input.

The user may also change the tables of an existing layout from one typeof PV module (or table type) to another. Such a change may be referredto as a technology swap. Technology swaps may be applied in manyexamples including when procurement challenges make a specific set ofmodules from a module vendor unavailable. Accordingly a user may swapsuch unavailable modules for modules from a different module vendor. Aslong as the newer modules are similar in size and characteristics as theswapped out modules, the design automation computer system willfacilitate such a technology swap.

As layouts are stored on suitable storage, the design automationcomputer system may efficiently re-render a pre-rendered layout. Thedesign automation computer system may also allow a user to remove allstored layout result sets and restart the process. Further, a user mayremove a specific set of layout result sets which may not be relevant.The design automation computer system also allows for exporting layoutresult sets into suitable output. In one example, such output may be ina human-readable tabular form to allow comparison using external tabularviewers.

The design automation computer system identifies a layout starting pointon the region boundary. The layout starting point may be any suitableedge of the region boundary as previously defined. The design automationcomputer system simulates placing (or “tiling”) PV blocks or tables inrows and columns based on the defined PV layout preferences. Morespecifically, the design automation computer system may apply PV tablesor blocks in east-west rows and north-south columns. In most examples,the design automation computer system avoids any obstructions, or otherimpediments in applying the first layout algorithm. Layout is completedwhen the maximum system size is reached or when the layout region iscovered with PV tables or blocks in a manner consistent with PV layoutpreferences. The completed layout may be stored for later comparison.The completed layout is further rendered as a three-dimensional sitemodel by the design automation computer system.

As may be apparent, a variety of layouts may be generated depending on,for example, starting points, spacing between blocks and tables, andother variables. Depending upon the previously identified layout detail,the design automation computer system determines whether additionalcompleted layouts are required and generates further layouts.

On generating all completed layouts, the design automation computersystem may store the completed layouts as completed layout options. Thedesign automation computer system sorts the completed layout options byeither energy output or total system size. The design automationcomputer system facilitates a review of completed layout options by theuser. Specifically, the design automation computer system presents anoptimal (or preferred) layout to the user. The user may select theoptimal layout or alternately review other options.

Alternatively, the selected PV system type is a parking canopy. In atleast some examples, parking canopies use an alternative layout method.The design automation computer system receives the selection of theparking canopy system type. In most examples, parking canopies are laidout along a parking row axis. The design automation computer systemreceives graphical user input identifying parking row axes. The designautomation computer system may determine canopy table spacing(determined based on, for example, logistical and maintenance reasons)and determine suitable table placement along the defined parking rowaxes. In at least some examples, the design automation computer systemalso receives orientation information for the canopies to allow the PVmodules on the parking canopy to have greater exposure to solarirradiance. By collecting and determining these PV layout preferences,the design automation computer system determines the layout of blocks ortables in the parking canopy. However, in at least some examples, thedesign automation computer system may utilize an iterative process oftable or block layout in parking canopies similar to the processdescribed for ground mount and rooftop system types.

Upon determining the PV module layout, the design automation computersystem further determines an integrated structural layout. Theintegrated structural layout defines system component and the placementand integration of any structural components needed to support the PVsystem. The design automation computer system retrieves the previouslydetermined PV module layout and identifies sub-arrays within the PVmodule layout. Sub-arrays are defined as any grouping of PV modules thathave spacing between modules exceeding the standard spacing.

The design automation computer system retrieves structural componentsassociated with the PV module layout from the component library. Asecond layout algorithm is used to iterate through the PV module layoutand place structural components. Structural components are placedfactoring in rules and tolerances for modules and structures, receivedfrom the component library. Upon completion, the second layout algorithmgenerates an integrated PV structure/module layout (“PV structurelayout”). The design automation computer system also determines anelectrical design and an electrical layout. The design automationcomputer system receives a user selection indicating whether the PVsystem uses a central inverter.

The design automation computer system offers a broad-spectrum ofelectrical design tools extending from full automation to manual design,allowing the user a range of flexibility, speed and control. Severaltools are used to group modules into electrical strings based on thestring size identified by the user. Further, several equipment placementtools supplement such grouping tools. The design automation computersystem may implement the use of such supplemental tools when theelectrical configuration is determined (i.e., when thestring-to-inverter configuration is determined.)

If the user selects a central inverter, the design automation computersystem provides a selection of PV combiner options retrieved from thecomponent library. The user may select a PV combiner from the PVcombiner options. The design automation computer system determines arecommended quantity of strings per combiner based on the PV combinerbox and the PV module.

Similarly, if the user selects a central inverter, the design automationcomputer system may provide a selection of PV re-combiner optionsretrieved from the component library. The user may select a PVre-combiner from the PV re-combiner options. The design automationcomputer system determines a recommended quantity of strings perre-combiner based on the PV combiner box and the PV module.

Whether the user selects a central inverter or not, the user selects astring size based on the recommendations of the string size calculator.The design automation computer system receives the string size selectionand prompts the user for a target ratio of direct current to alternatingcurrent (DC/AC ratio). Accordingly, the user may reconfirm the stringsize previously identified during the creation of a table. The user mayadditionally select the number of strings per inverter (if a stringinverter is selected) or the number of strings per combiner (if acentral inverter is selected). The design automation computer systemreceives the DC/AC ratio and determines string-to-inverterpossibilities. More specifically, the design automation computer systemdetermines the number of strings in the PV module layout, and assignseach string to an inverter. Further, the design automation computersystem repeats the string-to-inverter matching process for a variety ofinverters. Because inverter types and sizes vary, manystring-to-inverter possibilities may be generated. Thestring-to-inverter possibilities are sorted by either DC/AC ratio or byinverter quantity. The design automation computer system prompts theuser for a selection of design configurations (i.e., astring-to-inverter configuration) and receives a design configurationselection.

String Grouping

In a first example, the design automation computer system allows a userto use a “Selection Order” tool. The design automation computer systemmay make Selection Order available when a user chooses the inverter (inthe case of string inverters) or combiner (in the case of centralinverters) desired to group modules into strings.

Initially, a user may activate the Selection Order tool and designatemodules desired to be strung together in a particular order. The designautomation computer system (and specifically, the Selection Order tool)renders the quantity of modules selected in a status bar as the usernavigates along module rows. The design automation computer systemallows the user to group the selected modules into one or more stringsin a preferred order. The Selection Order tool accordingly allows a userto have control over the string grouping process by allowing the user tochoose not only which modules are included, but the order in which theyare included, and therefore, the direction of the string wiring as itconnects all of the modules within the string.

In a second example, the design automation computer system allows a userto use a “Pre-Select” tool. The design automation computer system maymake Pre-Select available when a user chooses the inverter (in the caseof string inverters) or combiner (in the case of central inverters)desired to group modules into strings.

Initially, a user may select a group of modules and activate thePre-select tool. The design automation computer system renders aquantity of modules in a status bar and the user may either add orremove modules from the selection set. The design automation computersystem further allows the user to group the selected modules into one ormore strings. The design automation computer system determines the orderof the grouping and wiring using an algorithm that that connects moduleswhile minimizing jumpers between module rows and columns. In an exampleembodiment, such an algorithm accordingly connects the modules in a“zig-zag” manner. The Pre-Select tool provides a faster implementationof string grouping.

In a third example, the design automation computer system allows a userto use a “Auto (Min Wiring)” tool. The design automation computer systemmay make Auto (Min Wiring) available when a user chooses the inverter(in the case of string inverters) or combiner (in the case of centralinverters) desired to group modules into strings.

The design automation computer system allows a user to indicate the twodirections in which the string grouping should commence (e.g., upwardsand leftwards). The design automation computer system successivelygroups modules into strings based on the string size and the indicatedtwo directions. The design automation computer system completes theprocess when all strings for the given inverter or combiner are filledor if a large gap is found in the layout.

In order to minimize jumper wiring, the algorithm stops and turns when alarge gap between modules is encountered. Accordingly, in some examples,some of the modules within the layout may not be utilized for stringsbecause they are beyond the threshold of allowable jumper wire length.In such examples, the design automation computer system allows suchmodules to be grouped into strings using Pre-select or Selection Order,or to remove them entirely from the layout.

In a fourth example, the design automation computer system allows a userto use a “Auto (Max KW)” tool. The design automation computer system maymake Auto (Max KW) available when a user chooses the inverter (in thecase of string inverters) or combiner (in the case of central inverters)desired to group modules into strings.

The design automation computer system allows a user using the Auto (MaxKW) tool to selects a single module representing the starting point(e.g., a corner of the layout) of the modules that will be grouped intostrings for a particular string inverter or combiner. The designautomation computer system allows a user to indicate the two directionsin which the string grouping commences. The design automation computersystem groups modules successively into strings based on the string sizeand the indicated directions. The design automation computer systemcompletes the process when all strings for the given inverter orcombiner are filled. In contrast to Auto (Min Wiring), this algorithmallows for large gaps (and therefore long string jumper wires) in orderto ensure that modules within the layout are grouped into a string. Inthat respect, this algorithm tends to maximize the system size (or KW)throughout the electrical design process.

In a fifth example, the design automation computer system allows a userto use a “Full Auto” tool. The Full Auto may be used with either of MinWiring or Max KW. The Full Auto tool accordingly applies theabove-described Auto tools (Min Wiring or Max KW) to the completelayout. Accordingly, while the previous algorithms only work for asingle string inverter or combiner, the Full Auto tool processesthroughout the full layout and returns a completely grouped stringlayout.

Electrical Equipment Placement

Similar to grouping, the design automation computer system may placeelectrical equipment manually or automatically. Once the grouping iscompleted (i.e. all strings are identified), the design automationcomputer system automatically places components dependent on the type ofsystem (e.g., string inverters for string inverter systems, combinersand central inverters for central inverter systems). The designautomation computer system places each type of component in a locationthat minimizes shade on the modules and minimizes the length ofconductors feeding it. In each of the several cases (described below),the design automation computer system places components immediately forthe entire site. After the design automation computer system makes suchan automatic placement, the user may review and revise the placement asthey see fit.

In a first case, the design automation computer system groups stringinverters together in a single location on the site or in a distributedmanner throughout the module layout depending on user preference. Onsmaller sites, the system designer might prefer to have all stringinverters co-located and would choose a “Grouped” option and identify alocation. On larger sites, a user may select the “Distributed” optioncausing each string inverter to be placed automatically at the centroidof the physical location of its respective strings. In either case, thedesign automation computer system allows the location of each stringinverter to be manually adjusted by the user.

In a second case, central inverters may be automatically distributedthroughout the array within “Inverter Enclosures” identified by theuser. Accordingly, the design automation computer system allows the userto identify such inverter enclosures. Inverter enclosures may containone or more inverters and may represent a concrete pad, pre-fabricatedskid or pre-fabricated enclosure depending on the preference of theuser. Regardless of the enclosure type, the design automation computersystem makes the initial placement at the centroid of the physicallocation of all the strings feeding that inverter. The user may thenadjust this location manually if needed.

In a third case, combiners may be automatically placed after centralinverter placement. The design automation computer system offers theuser an option to place the combiner at the centroid of the stringsfeeding it or offset from the centroid in the direction of itsrespective inverter. For the latter option, the combiner is still placedon one axis of the centroid of the string group but is shifted on theother axis such that the location is closer to the central inverter. Ineither case, the combiners may be moved or adjusted manually afterautomatic placement.

Wire Schedule

As soon as a complete circuit is made from modules to inverter, the DC(direct current) wire schedule tool is activated in the designautomation computer system. The DC wire schedule tool provides a list ofapplicable wires and their lengths. Therefore, the information in thelist may be used to connect strings to combiners/string inverters andfrom combiners to central inverters. In some respects, the DC wireschedule is similar to the Bill of Materials (described below) butfocused on determining the wire type and size based on estimated length,the equipment connected and applicable code/environmental factors. Aslong as there is a string identified and/or grouped, and the associatedstring inverter (or, alternately combiner or central inverter) is placedin the model, the design automation computer system provides a DC wireschedule populated with information. In the display of the DC wireschedule, each conductor segment of the circuit is broken out in thewire schedule. In one example, the distances are estimated using thedistance calculated based on component sums (using x-y components)between each end of the conductor. The design automation computer systemupdates the wire schedule (or DC wire schedule) based on any adjustmentsmade to the location of components or properties of components.

The DC wire schedule tool receives each conductor segment and uses itsproperties and the user settings to define several attributes of theelectrical system. In the example embodiment, the DC wire schedule tool(and, therefore, the design automation computer system) defines therequired current carrying conductor size, grounding conductor andconduit/raceway.

The required current carrying conductor size is determined in part basedon conductor segment properties received by the design automationcomputer system. Conductor segment properties include short circuitcurrent, ambient temperature, quantity of conductors in the givenraceway (conduit), conductor material (e.g., aluminum or copper),conductor resistance, and length of the segment.

The design automation computer system (via the DC wire schedule tool)determines the current carrying conductor (CCC) size based on theconductor segment properties described above. Generally, the CCC sizerefers to the minimum conductor size allowable by code. Several de-ratefactors may be applied to determine the minimum conductor size and thenumber of parallel conductors required to support the current of thecircuit when more than one conductor is required. Such de-rate factorsmay include temperature, conduit fill, and the like. The de-rate factorsmay be retrieved from a database associated with the design automationcomputer system or received by a user based on a prompt.

After the minimum CCC is found, user settings are applied to furtherrefine the minimum conductor selection. In one example, a user maydefine a minimum conductor size greater than the minimum required, inwhich case the conductor size in the wire schedule will be increased tothe user-defined minimum. In a second example, a user may define amaximum voltage drop that results in the minimum CCC size becoming outof compliance with voltage drop standards defined by the user. When themaximum voltage drop is exceeded, the design automation computer systemupsizes the conductor until the voltage drop on the circuit (asdetermined by the conductor length and wire resistance) is below themaximum voltage drop.

Once the CCC is set, the DC wire schedule determines the minimumallowable grounding conductor size based on code.

Once both the CCC and grounding conductor are defined, the DC wireschedule algorithm determines the minimum allowable conduit or racewaysize based on the previous determinations, applicable electrical codeand user-defined settings. For example, such settings may includeconduit type and a designation of whether or not a raceway is used inthe conductor segment.

Once a wire schedule is generated, the design automation computer systemallows a user to alter, individually for each circuit, the size, type orquantity of CCCs, grounding conductor size, or conduit size. At eachpoint of alteration, the design automation computer system executes codechecks and user threshold checks (e.g., verifying that maximum voltagedrop is not exceeded) to ensure compliance of the system. If the designautomation computer system determines that a user choice causes aconductor to be out of compliance, an error flag is generated that showsentries on the wire schedule table that are out of compliance.

The design automation computer system also allows a user to export theDC wire schedule at any time to an Excel-ready CSV file.

Conduit Routing

The design automation computer system also includes a conduit routingtool. The conduit routing tool may be used for conduits, wire trays, andany type of wire management or raceway system. The conduit routing toolmay also be applied to direct-buried cables. The conduit routing toolallows the design automation computer system (automatically or via userinput) to draw a path that conductors physically take within the systemlayout. The conduit routing tool is also used to inform the DC wireschedule. For example, when a conductor route is complete, the DC wireschedule tool receives the length of the route determined by the conduitrouting tool (rather than the estimated x-y component length) to computevalues including the minimum CCC size. In one example, the conduitrouting tool determines the conduit route based on user input. Forexample, a user may select the significant corners of the route (e.g.,essentially drawing connecting lines) between a child (e.g., string orcombiner) and a parent (e.g., string inverter, combiner, or centralinverter). If the user draws a route between a child and parent thatalready has a route extending to it, the user may alternately select theexisting route to have it act as a guide, such that the new route iscleanly drawn in parallel with the existing route. The automaticparallel routing may allow for more efficient design. Each new routerefreshes the wire schedule and enables the user to judge the impact ofrouting conductors a certain way throughout the layout.

The design automation computer system places components within the PVstructure layout and the PV module layout. As used herein, thestructural layout, the electrical design, the electrical layout, the PVmodule layout, and the bill of materials may all be referred to ascreating a general system layout or a “PV system model.” The PV systemmodel substantially defines a representation of the designed PV system.In one example, the placement of components is done manually andincorporates supplemental user input. In the example embodiment, theplacement of components is automated. Based on the placed components andthe selected design configuration, the design automation computer systemautomatically generates a wire schedule. Because component placements,component properties, system hierarchies, and electrical code are allknown, the design automation computer system requires no additionalinput to generate the wire schedule. In some examples, the designautomation computer system may receive specific physical paths forconductors designated by the user. Based on such input, the wireschedule may be altered or regenerated. Upon determination of the wireschedule, the design automation computer system may finalize theelectrical design and electrical layout.

The design automation computer system additionally may determine a listof components, materials, sub-assemblies, intermediate assemblies,sub-components, parts and the quantities to construct the PV system.This list may be referred to as the bill of materials. The designautomation computer system receives the previously determined structurallayout, electrical layout, and PV module layout and generates anintegrated model. The design automation computer system automaticallyidentifies all components within the integrated model. The designautomation computer system also retrieves the wire schedule andcalculates the total of all electrical components included in the wireschedule. The design automation computer system additionally retrievesinformation regarding each component from the component library. In someexamples, the design automation computer system also receives laborman-hours and cost data regarding installation and service costs for thearea of the PV system from a labor cost database. The design automationcomputer system additionally receives material cost data for thecomponents and electrical components from a material cost database. Thedesign automation computer system accordingly calculates the cost of allsystem components in the integrated model including material and laborcosts. As described above and herein, when changes are made to thesystem design (e.g., changes made to the electrical design that resultin new DC wire schedules or new conduit routing), the bill of materialsmay also be updated by the design automation computer system toincorporate such changes.

The design automation computer system also defines an energy productionmodel. The design automation computer system receives energy productionparameter definitions based on weather data and simulationspecifications. The energy production parameter definitions mayaccordingly incorporate local design data. The design automationcomputer system additionally receives the integrated layout anddetermines an estimated energy production and yield. The estimatedenergy production and yield is used to determine an overall energymodel.

The design automation computer system may further receive energy pricingdata and determine a financial model. By incorporating the bill ofmaterials and cost information, and the overall energy model, thefinancial model may include a cost estimation and a profitabilityanalysis.

A technical effect of the systems and methods described herein includeat least one of (a) enhanced quality of PV systems by identifyingpreferable PV system layouts through advanced simulation; (b) increasedefficiency in the design of PV systems; (c) reduced risk of structuraldamage to PV systems through simulations and use of local design data;and (d) improved profitability of the final system through optimizationof the PV system design.

More specifically, such technical effects can be achieved by performingat least one of the following steps: (a) receiving a set of site data,wherein the site data includes a set of location identifiers; (b)receiving a system type selection; (c) receiving a plurality of systemcomponent selections; (d) receiving a plurality of PV layoutpreferences; (e) determining, at the design automation computer system,a PV module layout by iteratively applying a first layout algorithm tothe set of site data and the plurality of PV layout preferences, the PVmodule layout defining a placement of a plurality of PV modules of a PVsystem; (f) determining a structural layout, an electrical design, andan electrical layout based on the PV module layout; (g) determining abill of materials based on the PV module layout, the structural layout,and the electrical layout; (h) defining a PV model using the structurallayout, the electrical design, the electrical layout, the PV modulelayout, and the bill of materials; (i) determining a set of locationdesign characteristics based on the set of site data; (j) retrieving aset of structural product rules; (k) identifying a subset of structuralproduct rules associated with the set of location designcharacteristics; (l) refining the structural layout based on the subsetof structural product rules; (m) receiving a set of boundary offsetsassociated with the set of site data; (n) receiving a set of obstructiondefinitions associated with the set of site data, the set of obstructiondefinitions including a set of obstruction heights and a set ofobstruction offsets; (o) determining a set of shadow setbacks based onthe set of obstruction definitions; (p) determining the PV module layoutbased on the set of shadow setbacks such that the shadow setbacks definea plurality of regions where the plurality of PV modules cannot beplaced; (q) identifying a set of obstructions based on the set ofobstruction definitions; (r) projecting a set of shadows for a pluralityof time periods based on the set of obstructions and a projected sunlocation for each of the plurality of time periods; (s) integrating theset of shadows into an integrated shadow setback area; (t) providing aplurality of first component options to a user device based on acomponent library, receiving a first component selection correspondingto one of the plurality of first component options, from the userdevice, retrieving, from the component library, a plurality of secondcomponent options associated with the first component selection,providing the plurality of second component options to the user device,and receiving a second component selection corresponding to one of theplurality of second component options, from the user device; (u)receiving one of a parking canopy type selection, a ground mount typeselection, and a rooftop type selection; (v) providing the plurality ofsystem component selections based on the system type selection; (w)receiving the plurality of PV layout preferences based on the systemtype selection; and (x) determining an energy simulation, a costestimation, and a profitability analysis based on the structural layout,the electrical design, the electrical layout, the PV module layout, andthe bill of materials.

Referring initially to FIGS. 1 and 2, a PV module is indicated generallyat 100. A perspective view of the PV module 100 is shown in FIG. 1. FIG.2 is a cross sectional view of the PV module 100 taken at line A-A shownin FIG. 1. The PV module 100 includes a solar laminate 102 (alsoreferred to as a PV laminate) and a frame 104 circumscribing the solarlaminate 102.

The solar laminate 102 includes a top surface 106 and a bottom surface108 (shown in FIG. 2). Edges 110 extend between the top surface 106 andthe bottom surface 108. In this embodiment, the solar laminate 102 isrectangular shaped. In other embodiments, the solar laminate 102 mayhave any suitable shape.

As shown in FIG. 2, the solar laminate 102 has a laminate structure thatincludes several layers 118. Layers 118 may include for example glasslayers, non-reflective layers, electrical connection layers, n-typesilicon layers, p-type silicon layers, and/or backing layers. In otherembodiments, solar laminate 102 may have more or fewer layers 118,including only one layer, or may have different layers 118, and/or mayhave different types of layers 118. The solar laminate 102 includes aplurality of solar cells (not shown), each of which converts solarenergy to electrical energy. The outputs of the solar cells areconnected in series and/or parallel to produce the desired outputvoltage and current for the solar laminate 102.

As shown in FIG. 1, the frame 104 circumscribes the solar laminate 102.The frame 104 is coupled to the solar laminate 102, as best seen in FIG.2. The frame 104 assists in protecting the edges 110 of the solarlaminate 102. In this embodiment, the frame 104 is constructed of fourframe members 120. In other embodiments the frame 104 may include moreor fewer frame members 120.

This frame 104 includes an outer surface 130 spaced apart from solarlaminate 102 and an inner surface 132 adjacent solar laminate 102. Theouter surface 130 is spaced apart from and substantially parallel to theinner surface 132. In this embodiment, the frame 104 is made ofaluminum. More particularly, in some embodiments the frame 104 is madeof 6000 series anodized aluminum. In other embodiments, the frame 104may be made of any other suitable material providing sufficient rigidityincluding, for example, rolled or stamped stainless steel, plastic, orcarbon fiber.

Some example methods and systems are performed using and/or includecomputing devices. FIG. 3 is a block diagram of an example computersystem 300, specifically design automation computer system 300. Morespecifically, design automation computer system 300 represents anexample embodiment of a design automation computer system. In theexample implementation, design automation computer system 300 includescommunications fabric 302 that provides communications between aprocessor unit 304, a memory 306, persistent storage 308, acommunications unit 310, an input/output (I/O) unit 312, and apresentation interface, such as a display 314. In addition to, or inalternative to, the presentation interface may include an audio device(not shown) and/or any device capable of conveying information to auser.

Processor unit 304 executes instructions for software that may be loadedinto a storage device (e.g., memory 306). Processor unit 304 may be aset of one or more processors or may include multiple processor cores,depending on the particular implementation. Further, processor unit 304may be implemented using one or more heterogeneous processor systems inwhich a main processor is present with secondary processors on a singlechip. In another implementation, processor unit 304 may be a homogeneousprocessor system containing multiple processors of the same type.

Memory 306 and persistent storage 308 are examples of storage devices.As used herein, a storage device is any tangible piece of hardware thatis capable of storing information either on a temporary basis and/or apermanent basis. Memory 306 may be, for example, without limitation,random access memory (RAM) such as dynamic RAM (DRAM) or static RAM(SRAM), read-only memory (ROM), erasable programmable read-only memory(EPROM), electrically erasable programmable read-only memory (EEPROM),non-volatile RAM (NVRAM), and/or any other suitable volatile ornon-volatile storage device. Persistent storage 308 may take variousforms depending on the particular implementation, and persistent storage308 may contain one or more components or devices. For example,persistent storage 308 may be one or more hard drives, flash memory,rewritable optical disks, rewritable magnetic tapes, and/or somecombination of the above. The media used by persistent storage 308 alsomay be removable. For example, without limitation, a removable harddrive may be used for persistent storage 308.

A storage device, such as memory 306 and/or persistent storage 308, maybe configured to store data for use with the processes described herein.For example, a storage device may store (e.g., have embodied thereon)computer-executable instructions, executable software components, systemcomponent data, PV system layouts, installation instructions, workorders, and/or any other information suitable for use with the methodsdescribed herein. When executed by a processor (e.g., processor unit304), such computer-executable instructions and/or components cause theprocessor to perform one or more of the operations described herein.

Communications unit 310, in these examples, provides for communicationswith other computing devices or systems. In the example implementation,communications unit 310 is a network interface card. Communications unit310 may provide communications through the use of either or bothphysical and wireless communication links. Communication unit 310provides communication to one or more element of the PV system.

Input/output unit 312 enables input and output of data with otherdevices that may be connected to design automation computer system 300.For example, without limitation, input/output unit 312 may provide aconnection for user input through a user input device, such as akeyboard and/or a mouse. Further, input/output unit 312 may send outputto a printer. Display 314 provides a mechanism to display information,such as any information described herein, to a user. For example, apresentation interface such as display 314 may display a graphical userinterface, such as those described herein. The communication device 310may include one or more analog I/O.

Instructions for the operating system and applications or programs arelocated on persistent storage 308. These instructions may be loaded intomemory 306 for execution by processor unit 304. The processes of thedifferent implementations may be performed by processor unit 304 usingcomputer implemented instructions and/or computer-executableinstructions, which may be located in a memory, such as memory 306.These instructions are referred to herein as program code (e.g., objectcode and/or source code) that may be read and executed by a processor inprocessor unit 304. The program code in the different implementationsmay be embodied in a non-transitory form on different physical ortangible computer-readable media, such as memory 306 or persistentstorage 308.

Program code 316 is located in a functional form on non-transitorycomputer-readable media 318 that is selectively removable and may beloaded onto or transferred to design automation computer system 300 forexecution by processor unit 304. Program code 316 and computer-readablemedia 318 form computer program product 320 in these examples. In oneexample, computer-readable media 318 may be in a tangible form, such as,for example, an optical or magnetic disc that is inserted or placed intoa drive or other device that is part of persistent storage 308 fortransfer onto a storage device, such as a hard drive that is part ofpersistent storage 308. In a tangible form, computer-readable media 318also may take the form of a persistent storage, such as a hard drive, athumb drive, or a flash memory that is connected to design automationcomputer system 300. The tangible form of computer-readable media 318 isalso referred to as computer recordable storage media. In someinstances, computer-readable media 318 may not be removable.

Alternatively, program code 316 may be transferred to design automationcomputer system 300 from computer-readable media 318 through acommunications link to communications unit 310 and/or through aconnection to input/output unit 312. The communications link and/or theconnection may be physical or wireless in the illustrative examples. Thecomputer-readable media also may take the form of non-tangible media,such as communications links or wireless transmissions containing theprogram code.

In some illustrative implementations, program code 316 may be downloadedover a network to persistent storage 308 from another computing deviceor computer system for use within design automation computer system 300.For instance, program code stored in a computer-readable storage mediumin a server computing device may be downloaded over a network from theserver to design automation computer system 300. The computing deviceproviding program code 316 may be a server computer, a workstation, aclient computer, or some other device capable of storing andtransmitting program code 316.

Program code 316 may be organized into computer-executable componentsthat are functionally related. Each component may includecomputer-executable instructions that, when executed by processor unit304, cause processor unit 304 to perform one or more of the operationsdescribed herein.

The different components illustrated herein for design automationcomputer system 300 are not meant to provide architectural limitationsto the manner in which different implementations may be implemented. Thedifferent illustrative implementations may be implemented in a computersystem including components in addition to or in place of thoseillustrated for design automation computer system 300. For example, insome embodiments, computing device includes a global positioning system(GPS) receiver. Moreover, components shown in FIG. 3 can be varied fromthe illustrative examples shown. As one example, a storage device indesign automation computer system 300 is any hardware apparatus that maystore data. Memory 306, persistent storage 308 and computer-readablemedia 318 are examples of storage devices in a tangible form.

In another example, a bus system may be used to implement communicationsfabric 302 and may include one or more buses, such as a system bus or aninput/output bus. Of course, the bus system may be implemented using anysuitable type of architecture that provides for a transfer of databetween different components or devices attached to the bus system.Additionally, a communications unit may include one or more devices usedto transmit and receive data, such as a modem or a network adapter.Further, a memory may be, for example, without limitation, memory 306 ora cache such as that found in an interface and memory controller hubthat may be present in communications fabric 302.

FIG. 4 is a block diagram of an example PV system 400. The PV system 400includes an array 402 of PV modules 100 and one or more inverters. Thearray 402 outputs AC power to one or more loads 404. A meter 406measures the power delivered to the loads 404. A gateway device 408,also referred to as a data acquisition device, a data logger, or a dataacquisition system (DAS), monitors the array 402 and transmits datacollected from the array 402 to a backend system 410 via a network 412.Backend system 410 includes one or more design automation computersystem 300. Backend system 410 is usually located at a second locationphysically separated from the first location at which PV system 400 islocated. Alternatively, the second system may be located at the samesite as the PV system 400. Moreover, the gateway device 408 may provideinformation to and communicate with more than one backend systems 410.The distance between the first location and the second location willvary among installed PV systems 400. In some embodiments, the firstlocation and the second location are greater than five miles apart. Inother embodiments, the first and second locations are more than tenmiles apart, 25 miles apart, 50 miles apart, 100 miles apart, 200 milesapart, or even located on different continents.

The array 402 may be any suitable array of PV modules 100 and one ormore inverters 414. For example, the array 402 may include a pluralityof PV modules arranged in strings of PV modules. Each string of modulesis connected to a single inverter to convert the DC output of the stringof PV modules to an AC output. Alternatively, or additionally, each PVmodule may be coupled to its own inverter 414 (sometimes referred to asa microinverter) positioned near or on the PV module to which it iselectrically coupled. In still other examples, a plurality of strings ofPV modules may be connected, directly or through one or more stringcombiners, to a single inverter 414, sometimes referred to as a centralor string inverter.

In embodiments that do not include microinverters, the array 402 mayinclude a direct current power manager (DCPM) coupled to each PV module.The DCPM performs, for example, maximum power point tracking (MPPT) forthe PV module. It may also selectively control (i.e., limit and/orincrease) the maximum power output of the PV module and/or control theconduction of bypass diodes based on temperature and bypass current. TheDCPM may also translates the output I-V curve of the PV module to a newI-V curve at which the output voltage does not vary with ambienttemperature.

In some embodiments, the array 402 includes one or more tracking devicesconfigured to selectively position the PV modules relative to the sun toattempt to maximize the solar energy incident on the PV modules overtime. Any other suitable arrangement of PV modules and inverter(s) maybe used, including combinations of the arrangements described above.

The gateway device 408 collects data concerning array 402, such as viaone or more sensors (not shown). The gateway device 408 is and/orincludes a computing device, such as design automation computer system300. The collected data may include any appropriate operational,situational, environmental, or other data related to the operationand/or condition of the array 402. For example, the gateway may monitorthe ambient air temperature around the array 402, the amount of sunlightincident on the array 402 (or one or more PV module), the output voltageand current of the array 402, the output voltage and current of each PVmodule, the output voltage and current of each inverter and/ormicroinverter 414, the surface temperature of the PV modules 100, etc.Moreover, in some embodiments, the gateway device 408 is incommunication with one or more components of the array 402. For example,the gateway device 408 may be in communication with one or moreinverters 414 in the array 402. Each inverter 414 may provide thegateway device 408 with, for example, its input voltage, its inputcurrent, its output voltage, its output current, etc. In someembodiments, the array 402 (and more particularly the inverters 414) maybe controlled via the gateway device 408.

In one example, the network 412 is the Internet. In otherimplementations, network 412 is any other suitable communicationnetwork, including, for example, a wide area network (WAN), a local areanetwork (LAN), a cellular network, etc. Network 412 may include morethan one network. For example, gateway device 408 may connect to theInternet through one or more other networks and/or interfaces, such as alocal area network (LAN), a wide area network (WAN), a home area network(HAN), dial-in-connections, cable modems, and high-speed ISDN lines.

FIG. 5 is a flow diagram of an example method of designing aphotovoltaic (PV) system as shown in FIG. 4, implemented by the designautomation computer system 300 (shown in FIG. 3). Design automationcomputer system 300 is configured to receive 510 a set of site data,wherein the site data includes a set of location identifiers.

Design automation computer system 300 is also configured to receive 520a system type selection. Design automation computer system 300 isfurther configured to receive 530 a plurality of system componentselections.

Design automation computer system 300 is additionally configured toreceive 540 a plurality of PV layout preferences. Design automationcomputer system 300 is also configured to determine 550 a PV modulelayout by iteratively applying a first layout algorithm to the set ofsite data and the plurality of PV layout preferences, the PV modulelayout defining a placement of a plurality of PV modules of a PV system.

Design automation computer system 300 is additionally configured todetermine 560 a structural layout, an electrical design, and anelectrical layout based on the PV module layout. Design automationcomputer system 300 is further configured to determine 570 a bill ofmaterials based on the PV module layout, the structural layout, and theelectrical layout. Design automation computer system 300 is additionallyconfigured to define 580 a PV system model using the structural layout,the electrical design, the electrical layout, the PV module layout, andthe bill of materials.

FIGS. 6-17 are detailed flow diagrams illustrating steps performed bydesign automation computer system 300 (shown in FIG. 3) to design a PVsystem.

Referring to FIG. 6, at initial setup 610, design automation computersystem 300 receives a set of site data 620. Set of site data 620represents a depiction of a geographic site considered as a location forthe PV system. Set of site data 620 may include drawings or renderingsof the geographic site. In one example, set of site data 620 includessatellite data 624 such as satellite images and terrain images. In asecond example, set of site data 620 includes computer-aided design(“CAD”) drawings or engineering data 622 indicating the features of thegeographic site. In a third example, set of site data 620 may representlocation identifiers including, for example, geographic coordinates suchas latitude and longitude coordinates. In such examples, designautomation computer system 300 may retrieve further data such assatellite images and terrain data by accessing an external systemcontaining geospatial data.

Design automation computer system 300 may also receive additional sitefeatures 626 that are not included in set of site data 620. For example,the geographic site may include a tree that is not visible or indicatedin set of site data 620. As the tree may be an obstruction relevant tothe design of the PV system, the user may identify the obstruction andprovide it to design automation computer system 300.

Design automation computer system 300 also receives a set of locationidentifiers and a north angle 630. The set of location identifierssubstantially identify the physical location associated with first setof site data 620. In at least some examples, the set of locationidentifiers are provided explicitly from a user device. In otherexamples, the set of location identifiers is derived from the set ofsite data using any suitable method including, for example, imageanalysis and metadata analysis.

Design automation computer system 300 also identifies a north angle forthe set of site data. In some examples, the north angle may beautomatically determined based on the set of location identifiers. Inother examples, the north angle may be provided explicitly from a userdevice.

Design automation computer system 300 determines local design data 640based on set of site data 620. Local design data 640 may be retrievedfrom a local database, an external system, or a plurality of externalsystems. Local design data 640 may include, for example and withoutlimitation, seismic load data, wind load data, snow load data, solardata, wetland area identification data, floodplain area identificationdata, soil data, and elevation data. Some examples of external systemsthat may be used to retrieve local design data 640 include engineeringsociety databases, government databases, and academic databases. In atleast one example, design automation computer system 300 utilizesapplication program interfaces (“APIs”) to access local design data 640from such external resources. In a further example, design automationcomputer system 300 aggregates local design data 640 from a plurality ofsources and stores such aggregated local design data 640 at anassociated local design database. Local design data 640 may bebeneficial in the design of PV systems, as described herein, to identifylocal variables and risks associated with the location of set of sitedata 620. For example, a first location may be associated with highwinds. When designing a parking canopy system in the first location,such high winds may shear PV modules from the canopy. Accordingly,structural components may be utilized to mitigate the risk of highwinds. In a second example, a second location may be associated withregular flooding. When designing a ground mount system in the secondlocation, structural components may be utilized to mitigate the risk offlooding.

Design automation computer system 300 also receives a system typeselection 650. More specifically, a user accessing design automationcomputer system 300 selects a type of PV system. In the exampleembodiment, the system type selection may be ground mount, rooftop, andparking canopy. In other examples, other system types may be selectedand configured in manners consistent with those described herein.

In at least some examples, design automation computer system 300 alsoreceives layout region identifications and designations. Morespecifically, a user may identify a portion of the geographic siteassociated with set of site data 620 for use with the designed PVsystem. In one example, the user may graphically identify a subsectionof the geographic site that may be used. In further examples, the usermay provide a name for the subsection. The user may design multiple PVsystems in the same geographic site. Therefore, identifiers may beuseful to distinguish each subsection associated with a distinct PVsystem.

Referring to FIG. 7, design automation computer system 300 may alsodefine boundary offsets 710 associated with set of site data 620.Defined boundary offsets 710 identify areas which cannot be utilized inthe layout of the PV system. Such boundary offsets 710 may be chosen forlogistical purposes (e.g., to allow maintenance crews to access the PVsystem easily) or any other reason. In one example, a rooftop system isselected and defined boundary offsets 710 allow a walking path aroundthe PV system for maintenance access. Defined boundary offsets 710 maybe identified graphically.

Design automation computer system 300 additionally may defineobstructions 720 associated with set of site data 620. Obstructiondefinitions 720 define any obstructions that are located at thegeographic site. Examples of obstruction definitions 720 may includeobstruction locations, obstruction heights 722, and obstruction offsets724. Obstruction locations and obstruction heights 722 may be providedexplicitly. Alternately, obstruction locations and obstruction heights722 may be determined by processing the set of site data using, forexample, image analysis. In at least some examples, design automationcomputer system 300 may identify obstructions and obstruction heights722 without user input. Obstruction offsets 724 reflect offsetsassociated with the obstruction. In at least some examples, obstructionoffsets 724 are determined because of maintenance requirements. In theexample embodiment, obstruction offsets 724 are provided by a user at auser device.

Using the set of obstruction definitions 720, design automation computersystem 300 determines a set of shadow setbacks. More specifically,design automation computer system 300 identifies the set of obstructions720 based on the set of obstruction definitions and uses a shadowrendering process 730 to project shadow effects on the geographic sitefor a plurality of time periods. Design automation computer system 300identifies simulation time periods and identifies a projected sunlocation for each time period. Using the projected sun location, designautomation computer system 300 projects the shadow effects of the sunand the set of obstructions on the geographic site. In at least someexamples, the user provides the time periods 732 (e.g., dates and times)for simulating such shadow effects. In further examples, multiple PVmodule heights 734 may be simulated to show varying shadow effects basedon the height of the PV modules. In such examples, the user may providepotential PV module heights 734.

In the example embodiment, design automation computer system 300 usestwo algorithms to render shadow effects. In a first example, a coarsealgorithm 740 is used. Coarse algorithm 740 identifies obstructionsbased on the set of obstruction definitions 720 and projects the shadowcaused by each obstruction based on the projected sun position vectorfor each period in the simulated time period. In the second example, afine algorithm 750 is applied to refine the output of coarse algorithm740. Fine algorithm 750 performs sun position ray tests at shortdistance increments (e.g., less than 6 inches) in order to create higherresolution shadow effects. Fine algorithm 750 therefore produces a moreprecise shadow effects through this detailed simulation.

Shadow effects represent areas where PV systems will not yield optimalenergy production (because of the temporary or total reduction in solarirradiance at the location). Accordingly, it may be undesirable to placePV modules where obstructions cause shadow effects. Design automationcomputer system 300 therefore integrates the set of shadow effect areasinto an integrated shadow setback area or a defined setback and offset760. Defined setback and offset 760 is used as negative space to definewhere the PV system should not be designed.

Referring to FIG. 8, design automation computer system 300 also receivesa plurality of system component selections 810, 820, 830, 840, and 850.System component selections 810, 820, 830, 840, and 850 represent theselections of equipment that will be used by the PV system for energyproduction and transfer. Accordingly, in most examples, systemcomponents 810, 820, 830, 840, and 850 include PV modules 810, PVinverters 820, PV combiners 830, conductors 840, and conduits 850. Inthe example embodiment, design automation computer system 300 identifiespotential system component selections from a component library 812. Asused herein, “component library” 812 refers to a data store thatcatalogues components used in PV system design. Component library 812includes definitions and identifiers for system components 810, 820,830, 840, and 850, structural components, and electrical components.Further, component library 812 identifies which components may be usedwith other components. (In at least some examples, some systemcomponents 810, 820, 830, 840, and 850 may only be used with a subset ofother available system components 810, 820, 830, 840, and 850.)Component library 812 may be stored in any suitable form.

In the example embodiment, component library 812 is stored in a databaseassociated with design automation computer system 300. In at least someexamples, component library 812 also includes schematic information,safety information, pricing information, and maintenance informationassociated with components. In further examples, component library 812may include estimated labor costs associated with components to identifythe cost of, for example, installation and maintenance.

Design automation computer system 300 provides a retrieved plurality offirst system component options to a user device based on componentlibrary 812. Upon a selection by the user, design automation computersystem 300 receives a first system component selection corresponding toone of the plurality of first system component options from the userdevice. In the example embodiment, the first system component optionsrepresent a set of PV module options 810. In other examples, othersystem components may first be presented to the user.

Upon receiving a first system component selection, design automationcomputer system 300 may constrain the available system component optionsbased on the first system component selection. As described above, atleast some components are associated with a subset of other componentsand therefore force a filtering of subsequent system component options.Design automation computer system 300 accordingly retrieves a pluralityof second system component options associated with the first systemcomponent selection from the component library. Design automationcomputer system 300 presents the plurality of second system componentoptions to the user device and receives a second system componentselection corresponding to one of the plurality of second systemcomponent options from the user device. In the example embodiment, thesecond system component options represent set of PV inverter options820. In other examples, other components may secondly be presented tothe user.

In a similar manner, design automation computer system 300 may present aplurality of system component options to the user device until allsystem component options are identified for the purposes of PV systemdesign. In other examples, only a subset of system components isselected and design automation computer system 300 automaticallyidentifies suitable system components for the remainder of the PV systemdesign. In an example embodiment, a user selects a PV module 810, a PVinverter 820, and a PV combiner 830 and design automation computersystem 300 automatically selects a conductor 840 and a conduit 850 anddetermines PV component selections 860.

Referring to FIG. 9, design automation computer system 300 also definesa PV module layout. A PV module layout represents a physical layout ofPV modules within the geographic site. In at least some examples, PVmodule layouts follow a hierarchical convention wherein a group of PVmodules may be identified as a single unit known as a “table”. A tabletypically has fixed dimensions in terms of PV modules. A table mayfurther be grouped into a “block”. Similarly, a block typically hasfixed dimensions in terms of PV tables.

To define the PV module layout, design automation computer system 300may receive a table identifier 910 from the user device to distinguishtables. Design automation computer system 300 further identifies a PVmodule type and PV inverter type for the table, previously selected bythe user, by receiving module selection 920.

Design automation computer system 300 calculates or determines arecommended “string size” 930 for the table by running a string sizealgorithm 932. A string size represents the amount of PV modules thatmay be laid out in a series (e.g., a column of the table). As stringsizes increase, potential open-circuit voltage outputs for the stringsimilarly increase. Design automation computer system 300 determines therecommended string size 930 by identifying and processing a plurality ofvariables. Design automation computer system 300 runs string sizealgorithm 932 by identifying a proximate weather station (e.g., anASHRAE station) and receiving meteorological data for the geographicsite based from the proximate weather station. In the exampleembodiment, the received meteorological data includes record high andrecord low temperatures for the geographic site. Design automationcomputer system 300 may be accessed using an associated API or a datafeed. Design automation computer system 300 also receives electricalproperties including open-circuit voltage and maximum power pointtracking ranges for the identified PV module and the identified PVinverter. The values for such electrical properties may be retrievedfrom the component library.

Based on such electrical properties and meteorological data, designautomation computer system 300 determines a recommended string size forthe PV module layout 930. In the example embodiment, the recommendedstring size is the quantity of PV modules in a string that results in anopen-circuit voltage that is within the maximum power point trackingrange during record low temperatures for the geographic site.

Design automation computer system 300 provides the recommended stringsize to the user via the user device and receives a user string sizeselection 940. The user may select the recommended string size or choosean alternate string size. In at least some embodiments, users may onlyselect string sizes that result in open-circuit voltage that is withinthe maximum power point tracking range during record low temperaturesfor the geographic site.

Design automation computer system 300 also receives a selection of anamount of modules in the table 950. The selection may represent aselection of strings per table or a selection of modules per table.

The user may further define customized layout properties for the table.Design automation computer system therefore receives additional tablecustomization 960. In at least some examples, such customized layoutproperties include PV module orientation, row counts, tilt angles of thePV module, and spacing between rows and columns of the PV table.

The PV string selection, the selection of an amount of modules in thetable, and the customized layout properties may be described as “PVlayout preferences.” Based on the PV layout preferences, designautomation computer system 300 determines the configuration of each PVtable 970.

As noted above, PV tables may be grouped into PV blocks. Referring toFIG. 10, design automation computer system 300 may receive a tableselection by the user to aggregate tables into blocks. Specifically,design automation computer system 300 may receive a table selection 1010of a defined PV table and a table configuration selection 1020. Thedesign automation computer may further receive a table spacing selection1030. Table spacing selection 1030 may be facilitated by table spacingalgorithm 1032. Such spacing may be useful to facilitate maintenance ofeach table. Based on such user input, design automation computer system300 defines blocks 1040.

Depending upon the selected system type, design automation computersystem 300 receives additional PV layout preferences. If the PV systemis of a ground mount or rooftop type, design automation computer system300 receives an additional distinct set of PV layout preferences.Referring to FIG. 11, design automation computer system 300 receives atable/block selection 1110 for the PV table or PV block being designed.Design automation computer system 300 also receives a layout modeselection 1120 indicating whether the module layout is “uniform” or“non-uniform”. When the layout mode is uniform, design automationcomputer system 300 may substantially automate the layout by repeatingPV module dimensions and spacing. When the layout mode is non-uniform,design automation computer system 300 may prompt the user device foradditional layout information identifying the variances in layout.Design automation computer system 300 also receives a layout alignmentselection 1130. Layout alignment selection 1130 represents the selectionof the axial orientation of the PV modules by the user 1132.Specifically, design automation computer system 300 receives an axialorientation from the user device. In the example embodiment, PV layoutis along a north-south axis. In an alternative embodiment, the userdevice may transmit any suitable axis of orientation 1132. Based on thelayout alignment selection, design automation computer system 300determines an azimuth value 1140. Design automation computer system 300also determines a recommended spacing between rows of the PV tables1150. The recommended spacing may be determined by running a shadeanalysis algorithm 1152 to simulate shadow effects caused by each row ofPV modules. In the example embodiment, shade analysis algorithm 1152 isrun over the winter and summer solstice periods between 10 AM and 2 PM.The row spacing is therefore determined by identifying the row spacingthat allows for shade-free rows of PV modules in the simulated timeperiods. Design automation computer system 300 receives a user selectionfor row and column spacing 1160. The user may adopt the recommendedspacing or select their own.

Design automation computer system 300 may receive additional spacingpreferences 1162 from the user device. Such additional spacingpreferences 1162 may be provided by the user for reasons includinglogistics and access. Design automation computer system 300 receives theuser selection for row and column spacing and the additional spacingpreferences as received user spacing selections. In some examples, theuser may additionally provide a maximum system size 1170 to indicatethat design automation computer system 300 should not layout a systemexceeding this defined system size. Design automation computer system300 also receives a layout region 1175 and receives a layout detailselection 1180 based at least partially on a received layout region1175. Received layout region 1175 describes a physical area where layoutoccurs within the geographic site. As described above, users maydesignate particular regions for layout. Layout detail substantiallyrepresents the amount of time that design automation computer system 300may execute to identify PV layout options. A higher value of layoutdetail may yield more PV layout options to consider. However, a highervalue of layout detail may require more time to process. Additionally,design automation computer system 300 may receive a layout region 1175to identify the specific portion of the geographic site that may be usedfor defining PV layout options. All received and determined elements1110, 1120, 1130, 1140, 1150, 1160, 1170, and 1180 are processed andused to apply layout algorithm 1190.

In the described example (wherein the PV system type is ground mount orrooftop), design automation computer system 300 uses the site data andthe plurality of PV layout preferences to determine the PV modulelayout. Referring to FIG. 12, design automation computer system 300iteratively applies a first layout algorithm to the set of site data andthe plurality of PV layout preferences. Design automation computersystem 300 identifies a layout starting point on the region boundary1210. The layout starting point may be any suitable edge of the regionboundary as previously defined. Design automation computer system 300simulates laying out (or “tiling”) PV blocks or tables in rows andcolumns based on the defined PV layout preferences. More specifically,design automation computer system 300 may apply PV tables or blocks ineast-west rows 1220 and north-south columns 1230. In most examples,design automation computer system 300 avoids any obstructions, gaps, orother impediments in applying the first layout algorithm and completinglayout 1240. Layout is completed 1240 when the maximum system size isreached or when the layout region is covered with PV tables or blocks ina manner consistent with PV layout preferences. Completed layout 1240may be stored 1242 for later comparison. Completed layout 1240 isfurther rendered as a three-dimensional site model 1250 by designautomation computer system 300.

As may be apparent, a variety of layouts may be generated depending on,for example, starting points, spacing between blocks and tables, andother variables. Depending upon the previously identified layout detail,design automation computer system 300 determines whether additionalcompleted layouts are required 1260 and generates further layouts(returning to 1210).

On generating all completed layouts 1240, design automation computersystem 300 may store the completed layouts 1280 as completed layoutoptions. Design automation computer system 300 sorts the completedlayout options 1270 by either energy output or total system size. Designautomation computer system 300 facilitates a review of completed layoutoptions by the user. The user further determines a selected PV modulelayout 1290 selected from the completed layout options.

Alternatively, the selected PV system type is a parking canopy. In atleast some examples, parking canopies use an alternative layout method.Referring to FIG. 13, design automation computer system 300 receives theselection of the parking canopy system type 1310. In most examples,parking canopies are laid out along a parking row axis. Designautomation computer system 300 receives graphical user input identifyingparking row axes 1320. Design automation computer system 300 maydetermine canopy table spacing (determined based on, for example,logistical and maintenance reasons) and determine suitable tableplacement along the defined parking row axes 1330. In some examples,design automation computer system 300 determines suitable tableplacement 1330 after determining canopy table spacing 1332.Specifically, design automation computer system 300 determines canopytable spacing 1332 (i.e., separation between each canopy table in thecanopy system) and determines canopy table placement 1330 at leastpartially based on such table spacing. In at least some examples, designautomation computer system 300 also receives orientation information1340 for the canopies to allow the PV modules on the parking canopy tohave greater exposure to solar irradiance. By collecting and determiningthese PV layout preferences, design automation computer system 300determines the layout of blocks or tables in the parking canopy 1350.However, in at least some examples, design automation computer system300 may utilize an iterative process of table or block layout in parkingcanopies similar to the process described for ground mount and rooftopsystem types.

Upon determining the PV module layout, design automation computer system300 further determines an integrated structural and modular layout.Referring to FIG. 14, the integrated structural and modular layoutdefines the placement of PV modules and system components and theplacement and integration of any structural components needed tofacilitate the PV system. Design automation computer system 300retrieves the previously determined PV module layout 1410 and identifiessub-arrays within the PV module layout 1430. In some examples, designautomation computer system 300 applies an algorithm 1432 to identifymodule groups with sub-array spacing and uses the results of appliedalgorithm 1432 to identify sub-arrays 1430 within the module layout.Sub-arrays are defined as any grouping of PV modules that have spacingbetween modules exceeding the standard spacing. Accordingly, designautomation computer system 300 may apply a spacing algorithm to identifymodule groups with sub-array spacing.

Design automation computer system 300 retrieves structural components1440 associated with the PV module layout from component library 1442. Asecond layout algorithm is used to iterate through the PV module layoutand place structural components 1450. Structural components are placedfactoring in rules and tolerances for modules and structures 1452,received from the component library. Upon completion, the second layoutalgorithm generates an integrated PV structure/module layout (“PVstructure layout”) 1460.

Design automation computer system 300 also determines an electricaldesign and an electrical layout. Referring to FIG. 15, design automationcomputer system 300 receives a user inverter selection 1510 indicatingwhether the PV system uses a central inverter.

If the user selects a central inverter, design automation computersystem 300 provides a selection of PV combiner options retrieved fromthe component library. The user may select a PV combiner from the PVcombiner options. The combiner box selection is received 1512 by designautomation computer system 300. The combiner box selection provided tothe user to make selection 1512 may be determined based on componentlibrary 1514. Design automation computer system 300 determines arecommended strings-per-combiner size 1516 based on the PV combiner boxand the PV module.

Whether the user selects a central inverter or not, the user selects astring size selection that may be based on the recommended string size.Design automation computer system 300 receives the string size selection1520 and prompts the user for a target ratio of direct current toalternating current (DC/AC ratio). Design automation computer system 300receives the DC/AC ratio 1530 and determines string-to-inverterpossibilities 1540. More specifically, design automation computer system300 determines the number of strings in the PV module layout 1542, andassigns each string to an inverter. Further, design automation computersystem 300 repeats the string-to-inverter matching process for a varietyof inverters. Because inverter types and sizes vary, manystring-to-inverter possibilities may be generated. Thestring-to-inverter possibilities are sorted 1550 by either DC/AC ratioor by inverter quantity. Design automation computer system 300 promptsthe user for a selection of design configurations (i.e., astring-to-inverter configuration) and receives a design configurationselection 1560.

Design automation computer system 300 determines component placement1570 within the PV structure layout and the PV module layout. In oneexample, the placement of components is done manually and incorporatessupplemental user input 1572. In the example embodiment, the placementof components is automated. Based on the placed components and theselected design configuration, design automation computer system 300automatically determines a wire schedule 1580. Because componentplacements, properties, system hierarchies, and electoral code are allknow, design automation computer system 300 requires no additional inputto generate the wire schedule. In some examples, design automationcomputer system 300 may receive specific physical paths for conductorsdesignated by the user. Based on such input, the wire schedule may bealtered or regenerated. Upon determination of the wire schedule, designautomation computer system 300 may finalize the electrical design andelectrical layout.

Design automation computer system 300 additionally may determine a listof components, materials, sub-assemblies, intermediate assemblies,sub-components, parts and the quantities to generate the PV system. Thislist may be referred to as the bill of materials. Referring to FIG. 16,design automation computer system 300 receives the previously determinedstructural layout 1610, electrical layout 1620, and module layout 1630and generates an integrated model. Design automation computer system 300automatically identifies all components within the integrated model1640. Design automation computer system 300 also retrieves wire schedule1652 and calculates the total of all electrical components included inthe wire schedule 1650. Design automation computer system 300additionally retrieves information regarding each component from thecomponent library 1662. In some examples, design automation computersystem 300 also receives labor cost data regarding installation andservice costs for the area of the PV system from a labor cost database1664. Design automation computer system 300 additionally receivesmaterial cost data for the components and electrical components from amaterial cost database 1666. Design automation computer system 300accordingly calculates 1660 the cost of all system components in theintegrated model including material and labor costs.

Design automation computer system 300 also defines an energy productionmodel. Referring to FIG. 17, design automation computer system 300receives energy production parameter definitions 1710 based on weatherdata and simulation specifications. Energy production parameterdefinitions 1710 may accordingly incorporate local design data 1712 andsupplementary meteorological data 1714. Design automation computersystem 300 additionally receives the integrated layout 1722 anddetermines an estimated energy production and yield 1720. The estimatedenergy production and yield is used to determine an overall energy model1730.

Design automation computer system 300 may further receive energy pricingdata and determine a financial model 1740. By incorporating the bill ofmaterials and cost information, the financial model may include a costestimation and a profitability analysis.

This written description uses examples to disclose various embodiments,which include the best mode, to enable any person skilled in the art topractice those embodiments, including making and using any devices orsystems and performing any incorporated methods. The patentable scope isdefined by the claims, and may include other examples that occur tothose skilled in the art. Such other examples are intended to be withinthe scope of the claims if they have structural elements that do notdiffer from the literal language of the claims, or if they includeequivalent structural elements with insubstantial differences from theliteral languages of the claims.

When introducing elements of the present invention or the embodiment(s)thereof, the articles “a”, “an”, “the” and “said” are intended to meanthat there are one or more of the elements. The terms “comprising”,“including” and “having” are intended to be inclusive and mean thatthere may be additional elements other than the listed elements.

As various changes could be made in the above without departing from thescope of the invention, it is intended that all matter contained in theabove description and shown in the accompanying drawings shall beinterpreted as illustrative and not in a limiting sense.

What is claimed is: 1-25. (canceled)
 26. A computer-implemented methodfor determining obstruction setbacks in a photovoltaic (PV) system basedon shadow simulations, the method implemented by a design automationcomputer system in communication with a memory, the method comprising:identifying a set of obstructions wherein the set of obstructionsincludes a set of obstruction elevations and a set of obstructiondimensions; simulating a set of shadow effects using a first coarseshadow algorithm based on the set of obstructions; refining the set ofshadow effects using a second fine shadow algorithm based on the set ofobstructions and the set of shadow effects; and defining a plurality ofobstruction setbacks based on the refined set of shadow effects.
 27. Themethod of claim 26, further comprising: identifying a projected sunposition vector for each of a plurality of simulated time periods;projecting a shadow caused by each of the set of obstructions based onthe projected sun position vector for each of the plurality of simulatedtime periods; simulating the set of shadow effects based on theprojected shadow.
 28. The method of claim 26, further comprising:simulating the set of shadow effects for a plurality of solsticeperiods.
 29. The method of claim 26, further comprising: identifying atleast one table height associated with the PV system; and simulating theset of shadow effects at least partially based on the at least one tableheight.
 30. The method of claim 26, further comprising: identifying atleast one of the set of obstructions as including a number of cornerssufficient to increase processing times; generating a simplifiedrepresentation of the at least one obstruction, wherein the simplifiedrepresentation includes a reduced number of corners than the at leastone of the set of obstructions; and simulating the set of shadow effectsusing the simplified representation.
 31. The method of claim 26, whereinrefining the set of shadow effects further comprises: performing aplurality of sun position ray tests to create higher resolution shadoweffects; and refining the set of shadow effects using the higherresolution shadow effects.
 32. The method of claim 31, whereinperforming the plurality of sun position ray tests further comprises:identifying a shadow area from the simulated set of shadow effects;dividing the shadow area into a plurality of squares; identifying acentral point in each of the plurality of squares; identifying a sunposition for a period of time associated with a particular sun positionray test; projecting a line from each central point to the sun position;and determining whether each line intersects with at least oneobstruction.
 33. A design automation computer system used fordetermining obstruction setbacks in a photovoltaic (PV) system based onshadow simulations, the design automation computer system comprising: aprocessor; and a memory coupled to said processor, said processorconfigured to: identify a set of obstructions wherein the set ofobstructions includes a set of obstruction elevations and a set ofobstruction dimensions; simulate a set of shadow effects using a firstcoarse shadow algorithm based on the set of obstructions; refine the setof shadow effects using a second fine shadow algorithm based on the setof obstructions and the set of shadow effects; and define a plurality ofobstruction setbacks based on the refined set of shadow effects.
 34. Thedesign automation computer system of claim 33, further configured to:identify a projected sun position vector for each of a plurality ofsimulated time periods; project a shadow caused by each of the set ofobstructions based on the projected sun position vector for each of theplurality of simulated time periods; simulate the set of shadow effectsbased on the projected shadow.
 35. The design automation computer systemof claim 33, further configured to: simulate the set of shadow effectsfor a plurality of dates including a solstice period.
 36. The designautomation computer system of claim 33, further configured to: identifyat least one table height associated with the PV system; and simulatethe set of shadow effects at least partially based on the at least onetable height.
 37. The design automation computer system of claim 33,further configured to: identify at least one of the set of obstructionsas including a number of corners sufficient to increase processingtimes; generate a simplified representation of the at least oneobstruction, wherein the simplified representation includes a reducednumber of corners than the at least one of the set of obstructions; andsimulate the set of shadow effects using the simplified representation.38. The design automation computer system of claim 33, furtherconfigured to: perform a plurality of sun position ray tests to createhigher resolution shadow effects; and refine the set of shadow effectsusing the higher resolution shadow effects.
 39. The design automationcomputer system of claim 38, further configured to: identify a shadowarea from the simulated set of shadow effects; divide the shadow areainto a plurality of squares; identify a central point in each of theplurality of squares; identify a sun position for a period of timeassociated with a particular sun position ray test; project a line fromeach central point to the sun position; and determine whether each lineintersects with at least one obstruction.
 40. Computer-readable storagemedia for determining obstruction setbacks in a photovoltaic (PV) systembased on shadow simulations, the computer-readable storage media havingcomputer-executable instructions embodied thereon, wherein, whenexecuted by at least one processor, the computer-executable instructionscause the processor to: identify a set of obstructions wherein the setof obstructions includes a set of obstruction elevations and a set ofobstruction dimensions; simulate a set of shadow effects using a firstcoarse shadow algorithm based on the set of obstructions; refine the setof shadow effects using a second fine shadow algorithm based on the setof obstructions and the set of shadow effects; and define a plurality ofobstruction setbacks based on the refined set of shadow effects.
 41. Thecomputer-readable storage media in accordance with claim 40, wherein thecomputer-executable instructions cause the processor to: identify aprojected sun position vector for each of a plurality of simulated timeperiods; project a shadow caused by each of the set of obstructionsbased on the projected sun position vector for each of the plurality ofsimulated time periods; simulate the set of shadow effects based on theprojected shadow.
 42. The computer-readable storage media in accordancewith claim 40, wherein the computer-executable instructions cause theprocessor to: simulate the set of shadow effects for a plurality of timeperiods.
 43. The computer-readable storage media in accordance withclaim 40, wherein the computer-executable instructions cause theprocessor to: identify at least one table height associated with the PVsystem; and simulate the set of shadow effects at least partially basedon the at least one table height.
 44. The computer-readable storagemedia in accordance with claim 40, wherein the computer-executableinstructions cause the processor to: identify at least one of the set ofobstructions as including a number of corners sufficient to increaseprocessing times; generate a simplified representation of the at leastone obstruction, wherein the simplified representation includes areduced number of corners than the at least one of the set ofobstructions; and simulate the set of shadow effects using thesimplified representation.
 45. The computer-readable storage media inaccordance with claim 40, wherein the computer-executable instructionscause the processor to: perform a plurality of sun position ray tests tocreate higher resolution shadow effects; and refine the set of shadoweffects using the higher resolution shadow effects.
 46. Thecomputer-readable storage media in accordance with claim 45, wherein thecomputer-executable instructions cause the processor to: identify ashadow area from the simulated set of shadow effects; divide the shadowarea into a plurality of squares; identify a central point in each ofthe plurality of squares; identify a sun position for a period of timeassociated with a particular sun position ray test; project a line fromeach central point to the sun position; and determine whether each lineintersects with at least one obstruction. 47-67. (canceled)